Built-in tools
The actions an agent can take, from reading files to running code and working across apps.
tools toolbox out of the box built in shell files platform capabilitiesOn this page
Tools turn a request into an actionFiles, code, and researchDocuments and generated outputsBusiness work and platform controlsMemory, guidance, and coordinationWhat is available to your agentTools turn a request into an action
A tool gives the agent an operation it can actually execute. It has a name, structured inputs, and a result. Reading a spreadsheet, running a script, creating a record, and inspecting a connected calendar are tool actions. The conversation lets you follow that work.
You can ask in ordinary language. You do not need to remember tool names. They are listed below so you can understand the platform's foundations and recognize them in activity details.
Files, code, and research
| Tool | What it enables |
|---|---|
file | Read and write workspace files, inspect images, and return a file in the conversation |
shell | Run commands and scripts in the agent's working environment |
storage | Store files beyond a working copy, fetch them, and create supported sharing links |
web | Search and retrieve public web information |
browser | Inspect and interact with web pages through the supported browser service |
The filesystem makes multi-step work possible: a tool can create a file that another tool reads. A script can process a source file and save a result for a later conversation. See persistent files and code execution.
Documents and generated outputs
| Tool | What it enables |
|---|---|
pdf | Read, fill, merge, and split PDFs, and create a PDF by printing a document written as HTML |
spreadsheet | Inspect spreadsheet and CSV files: list sheets, describe them, and read rows |
presentation | Inspect, preview, and export presentation decks |
media | Generate supported images, video, and audio |
The agent builds workbooks, decks, and reports by writing short programs in its sandbox, which gives it real formatting, formulas, and charts, then uses these tools to check, preview, and convert the result. These tools can work with the same workspace files. The available operations and providers determine which formats and generation options can be used. Model work and some operations consume credits; “built in” does not mean every task is free.
Business work and platform controls
| Tool | What it enables |
|---|---|
data | Manage user-owned business datasets, inspect their structure, and run supported reporting queries |
internal_app | Build, test, review, and install a workspace app when the builder is enabled |
external_app | Build and publish a separate website or web app with explicit data capabilities |
platform | Inspect or change supported profile, context, agent, access, and workspace settings |
notify | Send a supported notification to a person |
Platform administration uses the caller's permissions. Giving the agent a natural-language instruction does not make it an administrator. Apps contribute their own tools for the records they own — for example, the Dashboard app lets the agent inspect and arrange dashboard widgets; use those interfaces rather than treating every app table as a general dataset.
Memory, guidance, and coordination
| Tool | What it enables |
|---|---|
memory | Save, find, and remove remembered facts |
skills | Discover and load reusable instructions, and manage supported custom or installed skills |
plan | Track the steps of the task in the conversation |
ask_user_question | Ask for a decision or missing detail |
subagent | Delegate a bounded task and bring back its report |
cron | Create, inspect, run, or remove scheduled work |
activity | Look up what people and agents did in the workspace |
connector | Discover and invoke supported operations on connected services, and start a connection for you to complete |
Tools can be added to a conversation's available set when needed. The toolbox activation step loads a deferred tool or app toolkit; it does not execute the business action or grant new access.
What is available to your agent
Opser provides the platform tool foundation. The actual set depends on agent restrictions, workspace configuration, installed apps, connected accounts, and the task context. Some tools are scoped to a conversation or automation. App building and provider-backed services can be unavailable in an environment even though the platform supports them.
A skill tells the agent how to use a capability. It does not install missing software or authorize an account. When work is blocked, ask the agent to identify the unavailable tool, permission, connection, or service, then resolve that dependency.