Skip to main content
Glama

create_delivery_dispute_challenge

Create a stateless EIP-191 challenge using caller input only. First use action read and submit its signature to obtain the private binding. Include binding in every open/respond/close request. Challenge creation does not confirm operation or case existence, roles or eligibility. Sign only the exact expected origin, statement and consent text. No charge or automatic refund.

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>",
      "request": "<request>"
    },
    "name": "create_delivery_dispute_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses statelessness, input-only derivation, that no charge or automatic refund occurs, and that challenge creation does not confirm operation/case existence, roles or eligibility. It also adds a signing-safety warning (sign only the exact expected origin, statement and consent text). Gaps remain around expiry/replay and what the returned challenge looks like.

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?

Six short sentences, front-loaded with the what and the prerequisite workflow, with no filler. The telegraphic style ('No charge or automatic refund.') is efficient but slightly terse given the complexity of what is being signed.

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 multi-variant, deeply nested schema with no annotations and no output schema, the description covers the critical binding workflow, signing safety and non-confirmation caveats, but does not explain revision semantics, available reason/outcome values, evidence limits, or what the challenge response contains. Adequate but leaves real gaps for correct invocation of the non-read variants.

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?

Schema coverage is 0%, so the description must compensate for a large nested oneOf schema. It does explain the action lifecycle (read first, then open/respond/close) and the mandatory binding object, but leaves operationId, expectedRevision (clearly an optimistic-concurrency token), reason/outcome enums, evidenceHashes and detail undocumented. Partial compensation only.

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 first sentence names a specific verb and resource ('Create a stateless EIP-191 challenge') and scopes input to caller-supplied data. It is clearly a challenge-minting tool distinct from the submit/complete siblings, though it never explicitly names the sibling that consumes the challenge. Purpose is clear without needing 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 Guidelines4/5

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

It gives concrete sequencing guidance: use action 'read' first, submit its signature to obtain the private binding, and include that binding in every open/respond/close request. What is missing is explicit routing to alternatives (e.g., when to use submit_delivery_dispute_action instead) and any when-not-to-use condition beyond the eligibility caveat.

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