Skip to main content
Glama

ETOPS for Agents: Diversion-Reach Dispatch Certification

dispatch_release

Dispatch release $0.02 (first free once per account+wallet)

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": "dispatch_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsNo
class_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses only pricing ($0.02, first free once per account+wallet). Whether this is a write/mutating operation, what side effects it has, what permissions it needs, and what happens on failure are all unstated.

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?

A single short parenthetical aside is structurally compact and front-loaded, but its words are spent on billing rather than function. It is under-specified rather than verbose, which is a content problem more than a length problem.

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

Completeness1/5

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

No annotations, no output schema, zero parameter documentation, and a description that explains neither behavior nor inputs. For a 2-parameter dispatch tool this leaves the agent with essentially no basis for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters (legs array, class_id string), and the description mentions neither. The agent has no idea what shape 'legs' entries take or what 'class_id' refers to, leaving all parameter meaning undocumented.

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

Purpose2/5

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

The description restates the tool name verbatim ('Dispatch release') without explaining what a 'release' is in this domain or what dispatching it accomplishes. It distinguishes nothing from siblings like verify_release. The only added information is pricing, not purpose.

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, prerequisites, or alternatives are given. The agent is not told how this differs from verify_release, enroute_recheck, or record_legs, nor what conditions precede a dispatch. Cost information is present but does not guide tool selection.

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