Skip to main content
Glama

Inspect route

get_route
Read-onlyIdempotent

Read the stored record of a route you own: its status, provider attempts and payment exposure. Use it for the route itself after route_work or continue_route reserves one; for the live task view (current step, funds state) use get_route_task, and to preview without creating anything use plan_work. Requires a registered-agent API key with agent:read; limited to 60 calls per minute per agent. Routes owned by other agents return not found. Free.

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": {
      "route_id": "<route_id>"
    },
    "name": "get_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYesUUID of a route you own, from route_work, continue_route or get_route_task

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / route_id / description
      Previous value: -"Owned route UUID"New value: +"UUID of a route you own, from route_work, continue_route or get_route_task"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the auth requirement (registered-agent API key with agent:read scope), a concrete rate limit (60 calls/minute per agent), ownership scoping with a not-found error for other agents' routes, and cost (free). These are exactly the operational facts annotations cannot express.

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?

Purpose and scope are front-loaded, then alternatives, then operational constraints — a sensible order with no filler. It is dense, packing auth, rate limit, error behavior, and pricing into single clauses, which is efficient but slightly hard to scan; a light bullet structure would help without adding length.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description covers what is returned (status, provider attempts, payment exposure), prerequisites, failure mode, rate limits, and sibling routing. No external documentation is needed to call it correctly.

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 coverage is 100% and the single route_id property already documents that it is a UUID of an owned route sourced from route_work, continue_route, or get_route_task. The description repeats the ownership constraint but adds no format or validation detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

"Read the stored record of a route you own: its status, provider attempts and payment exposure" gives a specific verb, resource, and the exact contents returned, and it explicitly contrasts with get_route_task (live task view) and plan_work (preview). An agent can pick this tool without opening any schema.

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

Usage Guidelines5/5

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

It states when to call it (after route_work or continue_route reserves a route), names two siblings and the conditions that select them instead, and gives an explicit negative (preview-only work belongs in plan_work). Nothing is left to inference.

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