Skip to main content
Glama

approve_protocol

Approve a pending protocol proposal and register it in the protocol registry, optionally applying modifications and activating it immediately for governed agent sessions.

Instructions

Approve a pending protocol proposal and register it in the protocol registry.

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>",
      "proposalId": "<proposalId>",
      "reason": "<reason>"
    },
    "name": "approve_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesReason for approval
activateNoActivate the protocol immediately after registration (default: false)
projectDirYesAbsolute path to the project directory
proposalIdYesID of the proposal to approve
reviewedByNoWho is approving (default: orchestrator)
modificationsNoOptional modifications to apply to the protocol before registration

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden; it does disclose the core state transition (pending proposal becomes registered protocol), which is the most important trait for a mutation tool. It says nothing about permissions/authorization, irreversibility of approval, what happens to the proposal record afterward, or failure modes if the ID is invalid.

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?

A single compact sentence with the action and the outcome front-loaded and zero filler. Nothing is repeated or padded.

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

Completeness2/5

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

This is a six-parameter mutation tool with a free-form nested 'modifications' object, no annotations, and no output schema. The description does not say what is returned (e.g., the new protocol ID, which an agent would likely need to activate or query status), nor how the optional modifications object affects the approved result, leaving meaningful gaps for a tool of 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 description coverage is 100%, so the six parameters including reason, activate, reviewedBy, and modifications are already documented in the schema. The description adds no additional meaning such as how modifications interact with registration or when activate should be used instead of protocol_activate, so the baseline of 3 applies.

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?

The description names a specific verb ('Approve') and resource ('pending protocol proposal') and also states the second effect, registration in the protocol registry. An agent can distinguish it from propose_protocol or protocol_list, though it never names reject_protocol or protocol_register as explicit counterparts.

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 'pending' implies the precondition that the proposal must exist and be awaiting review, which is useful context. Beyond that there is no explicit when-to-use guidance, no statement of what to do for already-approved or rejected proposals, and no routing to alternatives such as reject_protocol or protocol_activate even though the tool has an activate option.

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