Skip to main content
Glama

ETOPS for Agents: Diversion-Reach Dispatch Certification

get_rating

Derived reach rating for a class

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

Input Schema

NameRequiredDescriptionDefault
class_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.5/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, and it discloses nothing. It does not state whether the rating is cached or recomputed, what happens if class_id is absent (the parameter is optional), whether it errors on unknown classes, or what permissions are required.

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?

It is short and front-loaded, but here brevity reflects under-specification rather than efficiency. Every word could stay and still leave the description inadequate.

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?

With no annotations, no output schema, and 0% parameter coverage, the six-word fragment carries the entire documentation load for the tool and fails to do so. Nothing about inputs, outputs, or behavior is recoverable.

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 description coverage is 0%, so the description must compensate for the single undocumented class_id parameter. The phrase 'for a class' weakly implies class_id is the input, but gives no format, source, or example of a valid class identifier.

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 is a noun phrase that largely restates the tool name: 'get_rating' becomes 'rating for a class.' It adds only the qualifiers 'derived' and 'reach' without defining what a reach rating measures or how it is derived, so the agent cannot confidently distinguish this from a generic lookup.

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?

No when-to-use guidance, no prerequisites, and no reference to the sibling tools (dispatch_release, verify_release, etc.) that might offer related data. The agent is left to guess at the caller's intent entirely.

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