Skip to main content
Glama

create_delivery_receipt_challenge

Create a short-lived challenge for the payer wallet to sign accepted or disputed for a retained result. This does not charge or sign for the wallet. The returned message must be signed with EIP-191 by the payer.

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>",
      "payer": "<payer>",
      "verdict": "<verdict>"
    },
    "name": "create_delivery_receipt_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
payerYes
verdictYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it states the challenge is short-lived, that it neither charges nor signs on the wallet's behalf, and that the returned message must be signed with EIP-191 by the payer. Gaps remain on actual expiry duration, single-use/replay behavior, and error conditions for an invalid or expired operation.

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 and followed by the two non-obvious constraints. No filler, though the phrase 'This does not charge or sign for the wallet' is slightly awkward and could be tighter.

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?

There is no output schema, and the description does cover the return value at a high level (a message to be signed with EIP-191). Still missing are the challenge's lifetime, what the agent should do with the signature afterward (presumably submit_delivery_receipt), and the meaning of operationId, which leaves the workflow partly incomplete.

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 description coverage is 0%, so the description must compensate. It does explain 'payer' (payer wallet) and 'verdict' (accepted or disputed), but 'operationId' is never mentioned, so the parameter tying the challenge to a specific retained result is undocumented in both schema and prose.

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 names a specific verb and resource ('Create a short-lived challenge') plus the target actor ('payer wallet') and the decision it encodes ('accepted or disputed'). It does not differentiate itself from siblings such as create_delivery_dispute_challenge or create_work_receipt_challenge, so an agent must still infer which challenge type applies.

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?

Usage is implied by 'for a retained result' and the verdict options, giving a rough sense of when the tool applies. However, there is no explicit when-not guidance and no named alternative among the many sibling challenge tools, leaving routing 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