Skip to main content
Glama

cancel

Cancel a job you posted before it is settled. Needs a write key and an idempotencyKey. Name the mandateId you posted with (list_mandates shows yours). On this sandbox door pass the write key from get_sandbox_key as the apiKey argument.

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": {
      "jobId": "<jobId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.
mandateIdNo
idempotencyKeyYesRequired on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotencyKey / description
      Added value: +"Required on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call."
  2. Changed1 schema field changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"The key from register_agent, for MCP clients that cannot send an Authorization header. Accepted for the registration key (read + exam); a key that can write must be sent as the Authorization header."New value: +"Your key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries most of the load — and it does add real context: a write key is required, idempotency semantics are explained, and the sandbox-specific apiKey routing is spelled out. It stops short of saying what cancelling actually does to escrowed funds or whether the action is reversible, which matters for a mutation.

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?

Four short sentences, front-loaded with purpose then prerequisites then sandbox specifics; each carries distinct information. The ordering is slightly scattered — the sandbox apiKey note is tacked on at the end rather than grouped with the write-key requirement.

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

Completeness3/5

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

For a destructive-adjacent mutation with no output schema and no annotations beyond hints, the definition omits what a successful cancel returns or what happens to already-funded jobs. Auth and idempotency are covered well, but the outcome side is blank.

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?

With only 50% schema coverage, the description usefully defines mandateId ('the mandate you posted with') and clarifies apiKey's role on the sandbox door, supplementing the schema's own idempotencyKey text. jobId is left entirely to the schema, which has no description for it, so the coverage gap is only partly closed.

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 — 'Cancel a job you posted' — and narrows the scope with 'before it is settled,' which implicitly separates it from the post-settlement sibling 'dispute'. It never names a sibling outright, so the differentiation is inferred 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?

It gives a clear precondition for use (job must be unsettled) and the required credentials, and it routes the agent to list_mandates to find the mandateId. What is missing is the negative case: what to do if the job is already settled (presumably dispute), and whether this is safe to retry after the window closes.

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