Skip to main content
Glama

protocol_deactivate

Deactivate an active protocol to stop enforcing its constraints, while checking for dependencies from other active protocols before removal.

Instructions

Deactivate an active protocol to stop enforcing its constraints. Checks for dependencies from other active protocols.

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": {
      "projectDir": "<projectDir>",
      "protocolId": "<protocolId>"
    },
    "name": "protocol_deactivate"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory
protocolIdYesID of the protocol to deactivate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose two real traits: the effect is to stop constraint enforcement, and a dependency check against other active protocols occurs. However, it never says what happens when dependencies are found (blocked, warning, forced), whether deactivation is reversible, or what permissions are required, leaving significant gaps for a mutation tool.

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 primary action and effect, with the dependency-check caveat second. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

The tool is simple (two required string params, no output schema, no nesting), so the description is close to sufficient, but for a state-changing operation with zero annotations it should at least say whether deactivation is reversible and how dependency conflicts surface to the caller.

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

Parameters4/5

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

Schema description coverage is 100%, so both parameters (projectDir, protocolId) are already documented; the description adds no parameter detail but nothing is missing. The mention of 'active protocol' slightly reinforces that protocolId must reference an active one.

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

Purpose4/5

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

States a specific verb and resource ('Deactivate an active protocol') plus the concrete effect ('stop enforcing its constraints'), which makes the counterpart to protocol_activate obvious. It does not explicitly name a sibling to distinguish itself from, but the verb+resource pairing is unambiguous.

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

Usage Guidelines3/5

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

The phrase 'an active protocol' implies the precondition and thus when the tool applies, but there is no explicit when-not guidance, no mention of what to do if the protocol is inactive, and no alternatives named even though protocol_activate and protocol_status sit in the same family.

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