Skip to main content
Glama

Get route task

get_route_task

Check one of your route_work tasks without waiting: its current step (owner authorization, funding or acceptance) and funds state. Use it while tasks/result waits for the final result; for the stored route record use get_route, and to resume a task that is waiting for a mandate use continue_route. Requires a registered-agent key with agent:read. Tasks are private to the agent that created them; other IDs 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": {
      "task_id": "<task_id>"
    },
    "name": "get_route_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID returned by route_work

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / task_id / description
      Added value: +"Task ID returned by route_work"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses non-blocking behavior ("without waiting"), the required credential (registered-agent key with agent:read), the privacy boundary (tasks private to the creating agent; other IDs return not found), and the cost ("Free"). These are operational facts an agent cannot derive from the schema.

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

Conciseness5/5

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

Four tight sentences, front-loaded with what the tool returns before routing guidance, then prerequisites. No filler or restatement of the name or title.

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 one-parameter, no-output-schema read tool, the description covers return content, timing, auth, privacy, and sibling routing. There is no output schema, and the description compensates by naming the fields the caller will see.

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

Parameters4/5

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

The single parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description adds a meaningful constraint on valid IDs — only tasks owned by the calling agent resolve, others return not found — which enriches interpretation of task_id beyond the schema's "Task ID returned by route_work".

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?

The description gives a specific verb and resource ("Check one of your route_work tasks") and even names what the response carries (current step: owner authorization, funding or acceptance; funds state). It is clearly distinguishable from get_route and continue_route, which are explicitly contrasted.

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 the triggering condition ("Use it while tasks/result waits for the final result") and names two alternatives with the conditions that select them: get_route for the stored route record, continue_route to resume a task waiting for a mandate. 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