Skip to main content
Glama

Submit work route

route_work
Idempotent

Routing step 2 of 3: submit work as an MCP task. Send a new request to save its objective for your linked owner to authorize, or send route_id with mandate_id to reserve a route you own under the owner's saved mandate. Preview candidates with plan_work first. Track progress with get_route_task, get the final result with the standard tasks/result method, and cancel with tasks/cancel while no checkout or trade exists. Requires MCP task augmentation (protocol 2025-11-25) and a registered-agent key with agent:read, marketplace:write and payments:write. Never funds, signs or accepts output. Reuse client_reference exactly after an uncertain response. Free.

Input Schema

NameRequiredDescriptionDefault
requestNoNew work: a canonical route request with the plan_work fields, without client_reference. Send either request alone, or route_id with mandate_id
route_idNoExisting route you own to reserve; send with mandate_id
mandate_idNoYour linked owner's saved payment mandate that authorizes 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. Changed4 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 that authorizes this route"
    • changedInput schema / properties / request / description
      Previous value: -"Canonical route request without client_reference"New value: +"New work: a canonical route request with the plan_work fields, without client_reference. Send either request alone, or route_id with mandate_id"
    • addedInput schema / properties / route_id / description
      Added value: +"Existing route you own to reserve; send with mandate_id"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing prerequisites (MCP task augmentation, protocol 2025-11-25, registered-agent key with agent:read, marketplace:write, payments:write), the cancellation boundary tied to checkout/trade state, and the idempotency retry rule. The 'Never funds, signs or accepts output' guarantee reinforces the non-destructive annotation rather than contradicting it. Minor gap: it does not say what the submitted task response contains, though that is partly deferred to get_route_task.

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 core action and mode split, then alternatives, then requirements. It is dense and a few clauses stack multiple facts per sentence ('Track progress with get_route_task, get the final result ..., and cancel with ...'), which slows parsing, but no sentence is wasted.

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 stateful, multi-step, nested-object tool with no output schema, it covers the full lifecycle: submission modes, prerequisites, progress, result retrieval, cancellation limits, and retry safety. An agent has enough to call it correctly and to know where to look for the outcome.

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 100%, so the baseline is 3, but the description adds real meaning about the oneOf exclusivity and about who acts on each field: 'request' saves an objective 'for your linked owner to authorize', while route_id is 'reserve[d] ... under the owner's saved mandate'. The client_reference retry semantics are restated from the schema, so the gain over the schema is modest, not decisive.

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 ('submit work as an MCP task') and then spells out both call shapes: a new 'request' whose objective the linked owner authorizes, or 'route_id' + 'mandate_id' to reserve an owned route under a saved mandate. An agent can distinguish the two modes and the sibling 'plan_work' without opening the 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?

Explicit sequencing: preview with plan_work first, track with get_route_task, fetch the result via tasks/result, cancel via tasks/cancel only while no checkout or trade exists. It names the alternatives and the precise conditions that select them, leaving nothing 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