Skip to main content
Glama

ETOPS for Agents: Diversion-Reach Dispatch Certification

verify_release

Verify a signed dispatch release

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
releaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Verify' hints at a non-mutating check, but the description does not disclose whether it operates on a locally supplied release or a stored one, whether it can fail, or what it returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded fragment with no padding, so nothing is wasted. But it is under-specified rather than concise — a four-word phrase for a tool with a nested input object leaves the reader without enough structure to act on.

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?

No annotations, no output schema, an undocumented nested parameter, and no statement of outcome or error behavior. For a verification tool with a structured input, an agent cannot determine inputs, results, or failure semantics from this definition.

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

Parameters2/5

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

Schema coverage is 0% and the single 'release' parameter is an opaque nested object with no described structure. The word 'signed' in the description is the only hint about the payload shape, and it does not compensate for the undocumented schema.

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

Purpose3/5

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

It states a verb ('Verify') and a resource ('a signed dispatch release'), so the general intent is legible. However, 'verify' is ambiguous (signature validation? completeness check?) and there is no differentiation from the obvious sibling dispatch_release, which an agent must distinguish against.

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?

No when-to-use guidance, no prerequisites, and no mention of dispatch_release or any alternative. The agent must guess whether verification is mandatory after a dispatch or optional.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources