Skip to main content
Glama

Report delivery

report_delivery
Destructive

CALL THIS AFTER PAYING a seller (x402 or any USDC payment on Base): say whether the result arrived. Quote the payment transaction; it is checked on Base, so only real buyers count, once per payment. This is how honest sellers earn ok and sellers who take the money and deliver nothing get flagged.

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>",
      "delivered": "<delivered>"
    },
    "name": "report_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesThe payment's transaction hash (0x…).
pay_toNoOptional: the wallet you paid.
deliveredYestrue if you got what you paid for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare write semantics (readOnlyHint=false, destructiveHint=true), and the description adds genuinely useful behavior: the transaction is verified on Base, only real buyers count, and one report is allowed per payment. That verification and uniqueness policy is context the annotations do not supply. It still does not say what happens to the caller's report or whether it can be retracted, which matters for an irreversible reputation-affecting write.

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?

Two tight sentences with the trigger front-loaded in caps and the incentive rationale compressed into the closing clause. The closing framing ("honest sellers earn ok") is slightly promotional but does justify why the report matters, so it largely earns its place.

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?

Three simple parameters and no output schema, so the burden on the description is moderate. It explains when to call and the verification policy, but never indicates what the caller gets back (a confirmation, an updated trust signal, a flag) or what happens on a rejected/failed verification, which leaves the round trip underspecified.

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 the baseline is 3, but the description adds real meaning beyond it: the tx value is on-chain verified and enforced as one-report-per-payment, which tells the caller the hash must belong to a genuine payment. The optional pay_to parameter is left unexplained in the prose and is only covered by the schema.

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 gives a concrete verb+resource pair: report whether a paid-for result arrived, tied to a payment transaction. It is clear enough to select without opening the schema, though it never distinguishes itself from the sibling report_outcome, so a caller could still hesitate between the two.

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?

"CALL THIS AFTER PAYING a seller (x402 or any USDC payment on Base)" gives an explicit precondition and trigger, and "once per payment" sets a hard usage limit. What is missing is any exclusion or pointer to alternatives (e.g. report_outcome or check_payment) for adjacent cases.

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