activate_domain
Register every tool in one domain at once when a task needs a whole capability area. Preview activations and evictions with a precheck before changing the session context budget.
Instructions
Register every tool in a single domain at once. Use this when a task needs a whole capability area; prefer search_tools or activate_tools when you only need a few specific tools, because activating a domain costs far more context. Domains: . Activated tools appear in the tool list immediately; if your client does not refresh its tool list, invoke them with call_tool. Activation draws on the session context budget: when the budget is full, least-recently-used tools are evicted to make room, and the response reports what was activated and what was evicted. Pass precheck: true to preview wouldActivate / wouldEvict without changing anything. Activated tools auto-deactivate after ttlMinutes (default 30; pass 0 for no expiry). Use reload_extensions first to include external plugin/workflow domains.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"domain": "<domain>"
},
"name": "activate_domain"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to activate (e.g. "debugger", "network") | |
| precheck | No | Dry-run mode: report wouldActivate / wouldEvict (LRU candidates that must be deactivated to make budget room) and the projected afterEvict budget, without activating or deactivating anything. | |
| ttlMinutes | No | Auto-deactivate after N minutes (default: 30, set 0 for no expiry) |