Skip to main content
Glama

activate_tools

Dynamically registers specific tools by name after search_tools so you can enable exactly the tools needed, regardless of the current base tier.

Instructions

Dynamically register specific tools by name, regardless of current base tier. Use after search_tools to enable exactly the tools you need. In search-tier sessions this is usually enough; use activate_domain when you need every tool in a domain. Activated tools appear in the tool list immediately. If tools do not appear after activation, use call_tool to invoke them directly.

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": {
      "names": "<names>"
    },
    "name": "activate_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesArray of tool names to activate (from search_tools results). Also accepts a JSON stringified array for clients that serialize arrays as strings.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / names / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "description": "JSON stringified array for MCP clients that serialize arrays as strings",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / names / description
      Previous value: -"Array of tool names to activate (from search_tools results)"New value: +"Array of tool names to activate (from search_tools results). Also accepts a JSON stringified array for clients that serialize arrays as strings."
    • removedInput schema / properties / names / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / names / type
      Removed value: -"array"
    • 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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the immediate observable effect ('Activated tools appear in the tool list immediately') plus a troubleshooting fallback to call_tool. It does not mention that activation may evict other tools under a budget (that only surfaces in the precheck parameter text) or whether activation persists across sessions, leaving some mutation-side behavior implicit.

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?

Four short sentences, each carrying distinct information (what, when, alternative, fallback), with the core action front-loaded. Slightly dense in the middle but no sentence is redundant.

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

Completeness4/5

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

There is no output schema and no annotations, so the description must explain outcome and routing, which it does: immediate visibility in the tool list, a fallback invocation path, and the domain-wide alternative. Only the budget/eviction consequence and session persistence are left unstated, which is a modest gap for a two-parameter activation tool.

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 coverage is 100%, so both parameters are already documented, including the precheck dry-run and its LRU eviction semantics. The description only reinforces that names come from search_tools results; it adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource — 'Dynamically register specific tools by name' — and adds the key scope qualifier 'regardless of current base tier'. It also names the sibling it is not (activate_domain for whole domains), so an agent can distinguish it 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?

It explicitly sequences the tool after search_tools, says 'In search-tier sessions this is usually enough', and names activate_domain with the condition that selects it (need every tool in a domain). It even gives a fallback path via call_tool if activation appears not to take effect.

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