Skip to main content
Glama

deactivate_tools

Deactivate previously activated tools to free context space without affecting base profile tools. Provide tool names to remove dynamically added tools.

Instructions

Remove previously activated tools to free context. Only affects dynamically activated tools (added via activate_tools, activate_domain, or extension activation), not base profile tools.

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": "deactivate_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesArray of tool names to deactivate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / names / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / names / type
      Removed value: -"array"
  2. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the key behavioral constraint that base profile tools are untouched. It omits what happens on unknown or already-inactive names (error vs silent no-op), whether the operation is idempotent, and any confirmation or rate-limit behavior.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and its purpose, then the scope caveat. No redundant or filler wording.

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?

For a one-parameter, non-destructive-scoped tool with no output schema, the description supplies the essential scoping rule. Missing only edge-case behavior (unknown names, no-op semantics), which is minor at this complexity.

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% and the single 'names' parameter is already documented, including the stringified-array alternative, so the description only loosely implies the parameter is a list of tool names. Baseline 3 applies since the schema does the work.

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 ('Remove previously activated tools') plus the benefit ('free context'), and the scope clause distinguishes it from its inverse, activate_tools, without needing the sibling's schema.

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

Usage Guidelines4/5

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

Explicitly scopes when it applies: only dynamically activated tools (from activate_tools, activate_domain, or extension activation), not base profile tools. It gives no explicit when-not guidance or error/precondition advice beyond that scope, so context is clear but incomplete.

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