1
---
2
title: Tools and toolkits
3
-description: Access 800+ toolkits through Tool Router
4
-keywords: [available tools, browse toolkits]
3
+description: Understand how tools and toolkits work in Composio
4
+keywords: [tools, toolkits, meta tools, context management]
5
---
6
7
-Tool Router gives your agent access to most Composio toolkits by default. For details on configuring which toolkits are available in a session, see [Users and sessions](/docs/users-and-sessions#enabling-toolkits).
7
+Composio offers 800+ toolkits, but loading all the tools into context would overwhelm your agent. Instead, your agent has access to 5 meta tools that discover, authenticate, and execute the right tools at runtime.
8
9
-## Toolkits and tools
10
-
11
-A **toolkit** is a collection of related tools for a service and a **tool** is an individual action your agent can execute.
12
-
13
-| Toolkit | Tools |
14
-|---------|-------|
15
-| `github` | `GITHUB_CREATE_A_COMMIT`, `GITHUB_ACTIVITY_LIST_STARGAZERS_FOR_REPO`, `GITHUB_SEARCH_REPO_S`, ... |
16
-| `gmail` | `GMAIL_SEND_EMAIL`, `GMAIL_FETCH_EMAILS`, `GMAIL_CREATE_EMAIL_DRAFT`, ... |
17
-| `linear` | `LINEAR_CREATE_LINEAR_ISSUE`, `LINEAR_UPDATE_ISSUE`, `LINEAR_CREATE_LINEAR_LABEL`, ... |
9
+## Meta tools
10
19
-## Available toolkits
11
+When you create a session, your agent gets these 5 meta tools:
12
21
-Browse all available toolkits in the [Composio platform](https://platform.composio.dev) under "All Toolkits". Each toolkit page shows its tools (with input and output parameters) and authentication methods supported for that toolkit.
13
+| Meta tool | What it does |
14
+|-----------|--------------|
15
+| `COMPOSIO_SEARCH_TOOLS` | Discover relevant tools across 500+ apps |
16
+| `COMPOSIO_MANAGE_CONNECTIONS` | Handle OAuth and API key authentication |
17
+| `COMPOSIO_MULTI_EXECUTE_TOOL` | Execute up to 20 tools in parallel |
18
+| `COMPOSIO_REMOTE_WORKBENCH` | Run Python code in a persistent sandbox |
19
+| `COMPOSIO_REMOTE_BASH_TOOL` | Execute bash commands for file and data processing |
20
23
-You can also list toolkits programmatically:
21
+Meta tool calls in a session are correlated using a `session_id`, allowing them to share context. The tools can also store useful information (like IDs and relationships discovered during execution) in memory for subsequent calls.
22
25
-<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
26
-<Tab value="Python">
27
-```python
28
-# Returns top 20 toolkits by default
29
-toolkits = composio.toolkits.get()
23
+### How it works
24
31
-for toolkit in toolkits:
32
- print(toolkit.name)
25
```
34
-</Tab>
35
-<Tab value="TypeScript">
36
-```typescript
37
-import { Composio } from '@composio/core';
38
-const composio = new Composio({ apiKey: 'your_api_key' });
39
-// ---cut---
40
-// Returns top 20 toolkits by default
41
-const toolkits = await composio.toolkits.get();
42
-
43
-for (const toolkit of toolkits) {
44
- console.log(toolkit.name);
45
-}
26
+User: "Create a GitHub issue for this bug"
27
+ ↓
28
+1. Agent calls COMPOSIO_SEARCH_TOOLS
29
+ → Returns GITHUB_CREATE_ISSUE with input schema
30
+ → Returns connection status: "not connected"
31
+ → Returns execution plan and tips
32
+ ↓
33
+2. Agent calls COMPOSIO_MANAGE_CONNECTIONS (because not connected)
34
+ → Returns auth link for GitHub
35
+ → User clicks link and authenticates
36
+ ↓
37
+3. Agent calls COMPOSIO_MULTI_EXECUTE_TOOL
38
+ → Executes GITHUB_CREATE_ISSUE with arguments
39
+ → Returns the created issue details
40
+ ↓
41
+Done. (For large results, agent can use REMOTE_WORKBENCH to process)
42
```
47
-</Tab>
48
-</Tabs>
43
50
-For details on browsing tools within toolkits and inspecting schemas, see [Fetching tools and schemas](/docs/fetching-tools).
44
+### What SEARCH_TOOLS returns
45
52
-<Callout type="info">
53
-Some toolkits require you to provide your own credentials. See [Using custom auth configs](/docs/guides/using-custom-auth-configuration).
54
-</Callout>
46
+`COMPOSIO_SEARCH_TOOLS` returns:
47
56
-<Callout type="info">
57
-Need a toolkit that doesn't exist? [Request it here](https://request.composio.dev/boards/tool-requests).
58
-</Callout>
48
+- **Tools with schemas** - Matching tools with their slugs, descriptions, and input parameters
49
+- **Connection status** - Whether the user has already authenticated with each toolkit
50
+- **Execution plan** - Recommended steps and common pitfalls for the task
51
+- **Related tools** - Prerequisites, alternatives, and follow-up tools
52
60
-## Default session behavior
53
+### Processing large results
54
62
-When you create a session, all toolkits are available:
55
+For most tasks, `COMPOSIO_MULTI_EXECUTE_TOOL` returns results directly. But when dealing with large responses or bulk operations, your agent uses the workbench tools:
56
64
-<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
65
-<Tab value="Python">
66
-```python
67
-session = composio.create(user_id="user_123")
68
-```
69
-</Tab>
70
-<Tab value="TypeScript">
71
-```typescript
72
-import { Composio } from '@composio/core';
73
-const composio = new Composio({ apiKey: 'your_api_key' });
74
-// ---cut---
75
-const session = await composio.create("user_123");
76
-```
77
-</Tab>
78
-</Tabs>
57
+- **`COMPOSIO_REMOTE_WORKBENCH`** - Run Python code in a persistent sandbox. Use for bulk operations (e.g., labeling 100 emails), complex data transformations, or when results need further analysis with helper functions like `invoke_llm`.
58
80
-Your agent can search and use tools from any toolkit. To restrict or configure which toolkits are available, see [Users and sessions](/docs/users-and-sessions#enabling-toolkits).
59
+- **`COMPOSIO_REMOTE_BASH_TOOL`** - Execute bash commands for simpler file operations and data extraction using tools like `jq`, `awk`, `sed`, and `grep`.
60
+
61
+## Toolkits and tools
62
82
-<Callout type="info">
83
-Triggers can be used alongside Tool Router to respond to events in connected apps. See [Triggers](/docs/triggers) for setup instructions.
63
+A **toolkit** is a collection of related tools for a service. For example, the `github` toolkit contains tools for creating issues, managing pull requests, and starring repositories.
64
+
65
+A **tool** is an individual action your agent can execute. Each tool has an input schema (required and optional parameters) and an output schema (what it returns). Tools follow a `{TOOLKIT}_{ACTION}` naming pattern, like `GITHUB_CREATE_ISSUE`.
66
+
67
+<Callout>
68
+If you know exactly which tools you need, you can [execute them directly](/docs/tools-direct/executing-tools) without meta tools.
69
</Callout>
70
+
71
+## Authentication
72
+
73
+Tools execute with the user's authenticated credentials. When a user connects their GitHub account, all GitHub tools run with their permissions.
74
+
75
+If a tool requires authentication and the user hasn't connected yet, the agent can use `COMPOSIO_MANAGE_CONNECTIONS` to prompt them.
76
+
77
+<Card icon={<Key />} title="Authentication" href="/docs/authentication">
78
+ Learn how Composio handles user authentication
79
+</Card>
80
+
81
+## Useful links
82
+
83
+<Cards>
84
+ <Card icon={<Blocks />} title="Browse toolkits" href="/toolkits">
85
+ Explore all available toolkits
86
+ </Card>
87
+ <Card icon={<BookOpen />} title="Fetching tools" href="/docs/toolkits/fetching-tools-and-toolkits">
88
+ Browse the catalog and fetch tools for sessions
89
+ </Card>
90
+</Cards>