Skip to main content
Glama

Continue route task

continue_route
Idempotent

Routing step 3 of 3: resume one of your route tasks after your linked owner saves a payment mandate. It binds the task's original route and context to that mandate and reserves at most one unpaid checkout. Use it when get_route_task shows the task waiting for a mandate; to start new work use route_work. Requires agent:read, marketplace:write and payments:write. Never funds anything or grants wallet authority. Reuse client_reference exactly after an uncertain response. 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>",
      "client_reference": "<client_reference>",
      "mandate_id": "<mandate_id>"
    },
    "name": "continue_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesYour route task ID from route_work
mandate_idYesYour linked owner's saved payment mandate for this route
client_referenceYesYour idempotency key (letters, digits, . _ : -). Reuse it exactly after an uncertain response to get the same task back instead of a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / client_reference / description
      Added value: +"Your idempotency key (letters, digits, . _ : -). Reuse it exactly after an uncertain response to get the same task back instead of a duplicate."
    • addedInput schema / properties / mandate_id / description
      Added value: +"Your linked owner's saved payment mandate for this route"
    • addedInput schema / properties / task_id / description
      Added value: +"Your route task ID from route_work"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=true), and the description adds context beyond them: required scopes (agent:read, marketplace:write, payments:write), the binding of the task's original route and context to the mandate, the 'at most one unpaid checkout' reservation, the explicit guarantee that it never funds anything or grants wallet authority, and the retry rule after an uncertain response. That is exactly the extra disclosure annotations cannot carry.

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?

Front-loaded with the step position and the action, then prerequisites, alternatives, scopes and guarantees in a tight sequence. Every sentence is functional, though 'Free.' and the restated idempotency rule are minor padding.

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?

Only three parameters, no output schema and no nested objects, and the description still covers the trigger, the alternative tool, the auth scopes, the side effect (checkout reservation), the non-effect (no funding, no wallet authority) and the retry semantics. Nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so the baseline is 3, and the description adds real meaning on top: mandate_id is framed as the linked owner's saved mandate that the original route and context get bound to, and client_reference reuse is tied to the idempotency guarantee. It repeats the reuse-after-uncertain-response rule that the schema also states, which is redundancy rather than new information.

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?

States a specific verb and resource ('resume one of your route tasks') plus the precondition ('after your linked owner saves a payment mandate') and positions itself as 'Routing step 3 of 3'. It explicitly separates itself from route_work ('to start new work use route_work'), so an agent can distinguish it from siblings without reading 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?

Gives an explicit trigger condition ('Use it when get_route_task shows the task waiting for a mandate') and names the alternative for the other case ('to start new work use route_work'). Prerequisites (linked owner must have saved a mandate) are stated rather than inferred.

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