Skip to main content
Glama

protocol_list

Lists registered protocols with status and summary details, optionally filtering to active ones and choosing compact or pretty output for project governance review.

Instructions

List all registered protocols with their status and summary information.

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>"
    },
    "name": "protocol_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'compact' for minimal output, 'pretty' for full formatting (default)
activeOnlyNoOnly show active protocols (default: false)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read operation. It says nothing about result size, whether all projects are listed, how the 'summary information' is shaped, or whether the call has side effects or permissions requirements.

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?

A single front-loaded sentence with no wasted wording, though 'summary information' remains vague and the sentence could have used its remaining space to disambiguate from sibling list tools.

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 simple three-parameter listing tool with full schema coverage and no output schema, the bar is low, but the description omits the projectDir scoping context and any sense of what a 'summary' contains, leaving an agent to rely entirely on the schema.

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 format, activeOnly, and projectDir are already documented in the schema, setting the baseline at 3. The description adds no filtering or formatting semantics beyond that, and notably never mentions that results can be restricted to active protocols only.

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 states a specific verb and resource ('List all registered protocols') and indicates the returned content (status and summary information), which is enough to distinguish it from mutation siblings like approve_protocol or protocol_register. It does not, however, differentiate itself from the closer read siblings such as protocol_status or discover_protocols.

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

Usage Guidelines2/5

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

There is no guidance about when to use this listing versus protocol_status, discover_protocols, or export_protocols, and no stated prerequisites or exclusions. An agent must infer the choice from the names alone.

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