Skip to main content
Glama

protocol_status

Retrieve detailed status for a specific protocol, including constraints, enforcement settings, recent violations, and audit history, to verify compliance and troubleshoot governance issues.

Instructions

Get detailed status of a specific protocol including its constraints, enforcement config, violations, and audit history.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditLimitNoMax audit entries to show (default: 10)
projectDirYesAbsolute path to the project directory
protocolIdYesID of the protocol to inspect
includeAuditNoInclude audit log entries (default: false)
violationLimitNoMax violations to show (default: 10)
includeViolationsNoInclude recent violations (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. The verb 'Get' and the returned field list signal a read, and the enumeration of constraints/violations/audit does convey scope, but nothing states that it is non-mutating, what happens when the protocolId is unknown, or how the audit/violation limits bound the response.

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?

It is a single front-loaded sentence with the resource stated first and the payload categories listed after; there is no filler. The trailing list of four content categories is slightly dense but each item conveys real scope.

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?

With six parameters, no output schema, and no annotations, the description does useful work by naming what the response contains, which substitutes partly for a missing output schema. It still leaves the safety profile and error behavior unstated for a tool with no annotation coverage.

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 all six parameters, including defaults and min/max bounds for auditLimit and violationLimit, are already documented. The description adds no meaning beyond that, 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 and resource ('Get detailed status of a specific protocol') and enumerates the payload categories: constraints, enforcement config, violations, audit history. That distinguishes it from the list-style siblings such as protocol_list, though it never names an alternative explicitly.

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 'a specific protocol' implies this is the per-protocol lookup rather than a listing tool, and the required protocolId reinforces that. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing against protocol_list, get_audit_log, or orchestrator_status, which all touch adjacent data.

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