Skip to main content
Glama

ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana)

dispute_packet_packet

$0.05 USDC on Solana per packet - the payment buys one signed dispute-evidence packet for the one paid call you name: the terms as quoted in the captured challenge, the payment as settled on-chain (verified under settlement-evidence/v1), the delivery artefact exactly as submitted with its service-computed body hash, timestamps, and an empty reverse-transaction field. The delivery leg is BUYER-SUBMITTED - NOT VERIFIED; the PAYMENT-RESPONSE header is UNSIGNED and stated so; adjudication is NOT offered.

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": {
      "challenge": "<challenge>",
      "paymentResponse": "<paymentResponse>",
      "delivery": "<delivery>"
    },
    "name": "dispute_packet_packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
deliveryYesThe delivery artefact AS RECEIVED: {status (integer 100-599), body (string) } or {status, bodyHash (64-hex SHA-256)} - exactly one of body / bodyHash. Buyer-submitted evidence, NOT verified by this service.
challengeYesThe captured 402 challenge object exactly as issued for the paid call being packeted. Processed in memory only, never stored.
timestampsNoOptional timestamps object {challenged_at?, paid_at?, delivered_at?}.
paymentResponseYesThe PAYMENT-RESPONSE header value from the paid call (base64 JSON string; a raw JSON string or the decoded object are also accepted). Processed in memory only, never stored.
settlementSignatureNoOptional explicit settlement reference (the settlement transaction signature). When absent, the header's transaction field is the settlement reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses the price ($0.05 USDC on Solana), that payment is settled on-chain and verified under settlement-evidence/v1, that the delivery leg is BUYER-SUBMITTED and NOT VERIFIED, that the PAYMENT-RESPONSE header is UNSIGNED, and that adjudication is explicitly out of scope. What it omits is failure behavior — what happens if payment fails, whether the charge is refundable, or what error surfaces on an invalid challenge.

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?

The price and the one-packet-per-paid-call constraint are front-loaded, and nearly every clause conveys distinct information (contents, verification status, signature status, scope exclusion). It is one long run-on sentence, though, and the dense parenthetical citation of settlement-evidence/v1 slows parsing.

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?

For a paid mutation tool with five parameters (three required, nested objects), no annotations, and no output schema, the description compensates well by describing the packet's returned contents — terms, on-chain settlement, delivery artefact with body hash, timestamps, empty reverse-transaction field — effectively standing in for a return-value schema. The remaining gap is operational: no mention of idempotency, retry, or what a failed settlement returns.

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 100%, so the baseline is 3 and the schema already explains challenge, delivery, paymentResponse and settlementSignature in detail. The description reinforces which inputs matter ('the terms as quoted in the captured challenge', 'the payment as settled on-chain', 'the delivery artefact exactly as submitted with its service-computed body hash') but adds no syntax, format, or precedence rules beyond what the schema states.

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?

States a concrete verb and resource: it buys one signed dispute-evidence packet for a single named paid call, and enumerates the packet's contents. The purpose is unmistakable, but it never names or contrasts itself with the sibling tools dispute_packet_precheck and dispute_packet_criteria, leaving the agent to infer the family relationship.

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: the phrase 'for the one paid call you name' scopes it to a single already-paid call, and 'adjudication is NOT offered' sets a boundary on what it is not for. However, there is no explicit instruction on when to call this versus dispute_packet_precheck or dispute_packet_criteria, and no prerequisites such as having a captured 402 challenge in hand.

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