Skip to main content
Glama

Delivery receipt

delivery_receipt
Read-onlyIdempotent

Verify APEX x402 delivery receipt and refund status by payment transaction hash. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "tx": "<tx>"
    },
    "name": "delivery_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYespayment transaction hash
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: a concrete price ($0.005 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the fact that omitting `payment` yields terms rather than a result. There is mild tension with readOnlyHint=true, since passing `payment` completes a purchase, but the tool's own action is verification/readout of an already-settled payment, so this reads as a payment handshake rather than a state mutation.

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?

Three tight sentences, front-loaded with the purpose, then cost, then the call sequence. No filler or repetition of the schema.

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

Completeness4/5

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

Covers purpose, cost, payment rails, and the two-call handshake for a two-parameter tool with no output schema. The only gap is that it never indicates what a successful verification returns (receipt state, refund status fields), though the description does name both things being checked.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains that `payment` is optional on the first call and that its absence returns terms to sign. That is workflow semantics the schema alone does not convey.

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

Purpose5/5

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

States a specific verb (verify) plus two concrete resources (APEX x402 delivery receipt and refund status) and the lookup key (payment transaction hash). An agent can tell this apart from the sibling arc_* / *_buy tools without opening 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?

Gives an explicit two-step call sequence: first call without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. That is clear operational context, but there is no explicit when-not-to-use guidance or named alternative for cases where the agent only wants receipt data without purchasing.

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