Toolsets
Group tools into collections — assign the right capabilities to the right agents
Toolsets
You have 50 tools and 20 agents. Your support agent needs CRM lookup and ticket creation. Your sales agent needs pricing and calendar booking. Assigning tools one by one? That doesn't scale.
A toolset is a named collection of tools. Create a "Customer Support" toolset, add the right tools, and any agent connected to that toolset's MCP endpoint gets exactly the capabilities it needs. Nothing more, nothing less.
How Toolsets Work
Every toolset gets its own MCP endpoint:
https://{workspace-slug}.chanl.dev/{toolset-slug}Connect an agent to acme.chanl.dev/support-tools and it gets support tools. Connect it to acme.chanl.dev/sales-tools and it gets sales tools. Same agent, different capabilities — controlled by which toolset you point it to.
Quick Start
Go to Build → Toolsets → Create Toolset. Give it a name and slug (URL-friendly identifier).
chanl toolsets create --name "Support Tools" --slug "support-tools"curl -X POST "https://api.chanl.ai/api/v1/toolsets" \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json" \
-d '{"name": "Support Tools", "slug": "support-tools"}'chanl toolsets add-tool --toolset support-tools --tool <tool-id>
chanl toolsets add-tool --toolset support-tools --tool <another-tool-id>Or in the dashboard: open the toolset, click Add Tool, and select from your workspace's tools.
Point your agent's MCP connection to the toolset endpoint:
{
"mcpServers": {
"chanl-support": {
"type": "streamablehttp",
"url": "https://acme.chanl.dev/support-tools",
"headers": { "X-API-Key": "your-api-key" }
}
}
}The agent now has access to only the tools in that toolset.
Built-in Admin Tools
Every workspace gets an admin-tools toolset automatically. It includes system tools for knowledge search, memory, agent management, and workspace stats. See the MCP page for the full list.
You can't delete admin-tools, but you can create custom toolsets that are more focused. A production support agent shouldn't have workspace_stats — it should have lookup_order and create_ticket.
Managing Toolsets
List toolsets
chanl toolsets listView tools in a toolset
chanl toolsets get support-toolsRemove a tool
chanl toolsets remove-tool --toolset support-tools --tool <tool-id>Toolset Strategy
| Agent Type | Toolset | Tools |
|---|---|---|
| Customer Support | support-tools | lookup_order, create_ticket, check_warranty, kb_search, memory_search |
| Sales | sales-tools | get_pricing, book_demo, check_availability, memory_search |
| Onboarding | onboarding-tools | create_account, send_welcome, kb_search, memory_add |
| Internal Admin | admin-tools | All system tools (built-in) |
System tools like kb_search and memory_search can be added to any toolset. You don't need to recreate them — they're shared across your workspace.