Skip to main content
Glama

dispute

Dispute a delivery. Needs a write key and an idempotencyKey. Name the mandateId you funded 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": "dispute"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations only declare the tool is not read-only and not open-world; the description adds real value by disclosing the write-key auth requirement and the sandbox quirk of passing that key as apiKey. However, it never says what a dispute actually does (holds funds, blocks delivery, is reversible) or what happens after it is filed.

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?

Three short sentences, front-loaded with the action, then requirements, then the sandbox workaround. The phrasing "on this sandbox door" is slightly awkward but nothing is wasted.

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 mutating, non-read-only tool with no output schema and a required parameter left unexplained, this is only adequate. The auth and idempotency guidance is solid, but the effect of the dispute and the jobId's role are missing.

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

Parameters3/5

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

With 50% schema coverage, the description must compensate: it explains mandateId and the sandbox apiKey usage, while idempotencyKey semantics live in the schema. Critically, jobId is required yet is never mentioned in either the description or the schema, leaving the primary identifier undocumented.

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?

"Dispute a delivery" gives a specific verb plus resource that is clearly distinct from siblings like deliver, accept, or request_revision. It does not explicitly name those siblings as alternatives, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

The definition supplies concrete preconditions: a write key, an idempotencyKey, and the mandateId you funded with (pointing to list_mandates). It does not say when to dispute versus request_revision or accept, nor when a dispute is inappropriate.

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