Skip to main content
Glama

submit_delivery_receipt

Submit the payer wallet's EIP-191 signature for a delivery receipt challenge. The signature must be created by the payer wallet, not by 402Mob.

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>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "submit_delivery_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYes
challengeIdYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • changedInput schema / properties / signature / pattern
      Previous value: -"^0x(?:[0-9a-fA-F]{128}|[0-9a-fA-F]{130})$"New value: +"^0x[0-9a-fA-F]{130}$"
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one important constraint - the signature must be produced by the payer wallet, not by 402Mob - but says nothing about what a successful submission accomplishes (receipt finalization, payment release), what happens on an invalid or replayed signature, or whether the action is idempotent or irreversible. For an unannotated mutation endpoint that gap is significant.

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

Conciseness5/5

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

Two short sentences with no waste, and the critical security constraint is placed immediately after the core action. Nothing is padded or redundant.

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 three-required-parameter mutation with no annotations and no output schema, the description establishes what to submit and who must sign it, but leaves the effect of submission, error behavior, and the operationId relationship unexplained. Adequate to start a call, not adequate to predict its consequences.

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 clarifies the meaning and provenance of the signature parameter (payer-wallet-produced EIP-191), which is genuine added value. However, challengeId and especially operationId (a UUID whose relation to the operation is never explained) are left entirely to their regex patterns, leaving two of three parameters semantically undefined.

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 ("Submit the payer wallet's EIP-191 signature for a delivery receipt challenge") and pins the artifact type (EIP-191 signature), which is enough to separate it from submit_work_receipt or the create_*_challenge siblings. It stops short of explicitly naming the sibling it is not, so it lands at a clear-but-not-differentiated 4.

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 rather than stated: mentioning a "challenge" signals that a challenge must exist first, but no tool is named (e.g., create_delivery_receipt_challenge) and no prerequisites, ordering, or exclusions are given. An agent can infer the sequence but must guess at it.

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