Every Composio session hands your agent a small set of meta tools instead of hundreds of raw tool definitions. The agent uses them to find the right tools for a task, connect the accounts those tools need, execute them, and process the results, all at runtime and all sharing one session_id.
This keeps your context window small: you load a handful of meta tools, not a catalog of 500+ apps. The agent searches for what it needs when it needs it.
A typical workflow runs in order: call COMPOSIO_SEARCH_TOOLS to discover tools and open a session, call COMPOSIO_MANAGE_CONNECTIONS if a toolkit is not yet connected, then run the tools with COMPOSIO_MULTI_EXECUTE_TOOL. Reach for the workbench and bash tools when responses are large enough to process out of context.
| Tool | What it does |
|---|---|
COMPOSIO_GET_TOOL_SCHEMAS | Returns the full input schema for tools you already know the slug for, so you can build schema-compliant arguments before executing |
COMPOSIO_MANAGE_CONNECTIONS | Checks connection status for a toolkit and returns a branded authentication link when the user needs to connect, covering OAuth, API keys, and every other auth type |
COMPOSIO_MULTI_EXECUTE_TOOL | Executes up to 50 tools in parallel and returns structured outputs ready for immediate analysis |
COMPOSIO_REMOTE_BASH_TOOL | Runs bash commands in a remote sandbox for file operations, data processing, and system tasks |
COMPOSIO_REMOTE_WORKBENCH | Runs Python in a persistent remote sandbox to process large remote files and script bulk or repeated tool executions |
COMPOSIO_SEARCH_TOOLS | Discovers the right tools across 500+ apps for a task and returns them with an execution plan, connection status, and the session_id that ties the rest of the workflow together |
These schemas are for reference only. We do not guarantee backward compatibility for parameter names or response shapes, so do not rely on them as structured type definitions in your code.