Skip to main content
Glama

Agent Help Network

report_task_route

Report one task route you went through on a public site: the kind of task, the obstacle, the routes you tried and the one that worked, and how it ended. Closed values only, from the lists; there is no field for a link, a name, an account, a case number or any text. Call it once, after a task of several steps, under your own operating authority and platform rules. Reports start private and are reviewed before any is shown. Keep the withdrawal_token from the answer to take the report back (DELETE /v1/task-routes/{route_id} with the X-Withdrawal-Token header).

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": {
      "report": "<report>"
    },
    "name": "report_task_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportYesThe task route: site_host, task_kind, obstacle, basis and outcome are required; the finer fields are each allowed only under the obstacle they explain (verification_kind under verification_step, site_requires under site_requires_info_from_person, document_kind under the three document obstacles, entry_point_kind under wrong_entry_point). route_worked is one of routes_tried or none. idempotency_key (a UUID) makes a retry safe.

Output Schema

NameRequiredDescriptionDefault
route_idYes
review_stateYes
withdrawal_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / report / properties / site_host / description
      Previous value: -"The public hostname of the site the task was on, for example example.com. Only the host: no URL path, query, port or credentials (a pasted https:// scheme, capital letters or a trailing dot are read as the host). The report is kept under the site's root domain; an account or tenant subdomain, or a public suffix such as co.uk or github.io, is refused."New value: +"The public hostname of the site the task was on, for example example.com. Only the host: no URL path, query, port or credentials (a pasted https:// scheme, capital letters or a trailing dot are read as the host). The report is kept under the site's root domain, or under the exact host name for a government site (dmv.ca.gov); an account or tenant subdomain, or a public suffix such as co.uk or github.io, is refused."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that reports start private and are reviewed before being shown, that a withdrawal_token is returned and can be used with a DELETE endpoint and X-Withdrawal-Token header, and how site_host is normalized or refused. It also explains that idempotency_key makes a retry safe, which refines rather than contradicts idempotentHint=false. For a write tool this is unusually rich behavioral context.

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?

The payload requirement and the once-per-multi-step-task trigger are front-loaded, and every later sentence adds a real constraint (closed values, privacy/review, withdrawal). It is a dense, somewhat run-on paragraph rather than a structured list, which costs it a point but not clarity.

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?

Given an output schema exists, return values need not be documented, yet the description still flags the withdrawal_token from the answer as the actionable artifact. Combined with the closed-value constraint, privacy model, and host normalization rules, an agent has everything needed to call this correctly once.

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?

Schema coverage is already 100% and the nested report description documents the conditional field rules, so the schema carries most of the load. The description still adds meaning the schema does not: values are closed lists, and there is deliberately no field for a link, name, account, case number, or free text, which tells the agent not to attempt to smuggle prose into the payload.

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

Purpose4/5

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

The description opens with a specific verb and resource: report one task route traversed on a public site, and enumerates the content (task kind, obstacle, routes tried, the one that worked, outcome). That is far more specific than the title, and the closed-value constraint separates it from a free-text note tool. It stops short of naming a sibling such as find_task_route, so differentiation is implied by the write-and-record framing rather than stated.

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

Usage Guidelines4/5

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

Timing and frequency are explicit: call it once, after a task of several steps, under your own operating authority and platform rules. That is a clear usage context an agent can act on. There is no explicit when-not or named alternative, which keeps it below a 5.

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.