Skip to main content
Glama

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

NameRequiredDescriptionDefault
domainYesDomain name to activate (e.g. "debugger", "network")
precheckNoDry-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.
ttlMinutesNoAuto-deactivate after N minutes (default: 30, set 0 for no expiry)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / precheck
      Added value: +{
      +  "description": "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.",
      +  "type": "boolean"
      +}
  2. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does so: effects on the tool list, the client-refresh caveat with the call_tool fallback, context-budget accounting with LRU eviction, response contents (activated/evicted), auto-expiry via ttlMinutes, and a dry-run mode. These are non-obvious, consequential behaviors an agent could not infer from the name or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and most sentences carry distinct operational facts. However, the fragment "Domains: ." is a broken enumeration with no values rendered, which wastes a clause and briefly misleads about whether a domain list should appear there.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description explains what the response reports (activated vs evicted) and how precheck changes it. For a three-parameter activation tool with budget side effects, nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents domain, precheck, and ttlMinutes. The description restates those semantics (precheck preview, 30-minute default, 0 for no expiry) but adds no format, validation, or naming conventions for the domain string beyond what the schema's example provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: "Register every tool in a single domain at once." It immediately distinguishes itself from search_tools and activate_tools, which target a few specific tools, so an agent can pick the right sibling without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("a task needs a whole capability area") plus explicit alternatives ("prefer search_tools or activate_tools when you only need a few specific tools") and the tradeoff driving that choice (context cost). It also names a prerequisite: run reload_extensions first for external plugin/workflow domains.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.