Skip to main content
Glama

protocol_activate

Activates a registered protocol to enforce its constraints while checking for conflicts with currently active protocols.

Instructions

Activate a registered protocol to begin enforcing its constraints. Checks for conflicts with currently 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_activate"
  }
}

Input Schema

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

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, the description carries the full burden. It usefully discloses one behavioral trait beyond the schema: that conflicts with currently active protocols are checked. It does not say what happens when a conflict is found (error, partial activation, override), whether activation is reversible, or what permissions are needed — significant gaps for a state-changing 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 action and followed by the notable side effect. No filler or redundancy.

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?

For a simple two-parameter mutation tool this covers the essentials, but with no annotations and no output schema, the description should say what activation returns and how conflicts surface to the caller. The omission of conflict-resolution behavior leaves the agent guessing about failure modes.

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 coverage is 100% with only two clearly documented parameters, so the schema does the work and the baseline is 3. The description adds the notion that projectDir scopes the activation target and protocolId must refer to a registered protocol, which gives marginal semantic value.

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 ("Activate a registered protocol") plus the effect ("begin enforcing its constraints"), which clearly separates it from propose_protocol, protocol_register, and protocol_deactivate. It stops short of naming an alternative, so it is strong but not maximally differentiated.

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 word "registered" implies the protocol must already exist before activation, giving an implicit prerequisite. However, there is no explicit statement of when to use this versus protocol_deactivate, approve_protocol, or protocol_register, and no note on what to do if activation is not desired yet.

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