Skip to main content
Glama

submit_delivery_dispute_action

Return challengeToken with the signature for an action or private read. Writes and their retries return only the original action acknowledgment. A fresh signed read returns private evidence and separate settlement/operation/delivery states. Seller responses remain possible after buyer closure.

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": {
      "operationId": "<operationId>",
      "challengeToken": "<challengeToken>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "submit_delivery_dispute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYes
challengeIdYes
operationIdYes
challengeTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

C2.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that write retries return only the original action acknowledgment, that a fresh signed read returns private evidence and separate states, and that seller responses remain possible after buyer closure. However, it omits key mutation details such as side effects, authorization requirements, and failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and avoids filler, but the first sentence is awkwardly structured and does not front-load a clear purpose. The later sentences carry useful behavioral detail but arrive before the agent knows exactly what the tool does.

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

Completeness2/5

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

For a four-required-parameter mutation tool with no annotations and no output schema, the definition is under-specified. It explains some write/read return behavior but does not provide enough parameter meaning, authorization context, or side-effect disclosure for an agent to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions challengeToken and signature but does not explain operationId or challengeId, leaving half of the required parameters undocumented in both schema descriptions and prose.

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

Purpose2/5

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

The description never clearly states that this tool submits a delivery dispute action. The opening sentence, 'Return challengeToken with the signature for an action or private read,' is vague and does not identify a specific verb plus resource, nor does it distinguish the tool from siblings such as create_delivery_dispute_challenge.

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

Usage Guidelines2/5

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

It implies two modes, writes and private reads, but gives no explicit guidance on when to use this tool versus alternatives. The statement about seller responses after buyer closure adds context but does not help select among the many sibling dispute/receipt/action tools.

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