Skip to main content
Glama

ETOPS for Agents: Diversion-Reach Dispatch Certification

enroute_recheck

En-route reach re-check $0.005

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

Input Schema

NameRequiredDescriptionDefault
anchor_aNo
anchor_bNo
class_idNo
positionNo
closed_idsNo
fields_by_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.3/5.0
Behavior1/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, yet it only states a price. It does not disclose whether the operation reads or mutates state, side effects, idempotency, auth requirements, rate limits, or return behavior.

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

Conciseness2/5

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

The description is very short, but it is under-specified rather than concise. The price is the only concrete detail, and no useful structure or priority information is provided for invoking the tool correctly.

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?

Given six parameters, nested object inputs, no annotations, and no output schema, the description is drastically incomplete. It omits everything an agent needs to use the tool safely and correctly.

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?

The schema defines six parameters with 0% description coverage, and the description adds no meaning for any of them. It does not explain anchor_a, anchor_b, class_id, position, closed_ids, or fields_by_id, leaving the agent unable to infer their purpose or format.

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 'En-route reach re-check $0.005' largely restates the tool name and adds a price, but does not state what is actually being re-checked, what resource is involved, or what the tool returns. It gives no differentiation from siblings like verify_release or dispatch_release.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The description provides no context, prerequisites, or alternatives.

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