Skip to main content
Glama

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

dispute_packet_criteria

The published criteria for the Dispute-Evidence Packet service (settlement-evidence/v1, packet form): the input contract, the packet legs, the honesty fences, and the pinned public test corpus identity. Read these before paying - every packet is reproducible from them. - no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/dispute-packet/criteria.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dispute_packet_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 burden and does disclose real behavior: it is free, requires no payment, raises no x402 challenge, and is reproducible/pinned. It does not say whether the response is JSON or text or how the corpus identity is formatted, which is a minor remaining gap.

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 purpose is front-loaded in the first clause, and the payment/endpoint notes are appended compactly. Some phrasing is jargon-heavy ("honesty fences", "packet legs") and could be plainer, but no sentence is pure filler.

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 zero-parameter documentation-fetch tool with no output schema and no annotations, the description covers what the payload contains, that it is free, and how to reach the equivalent endpoint. It omits only the response shape, which is a modest gap rather than a blocking one.

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?

The tool takes zero parameters and has an empty object schema at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; nothing is mis-specified.

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?

It states a specific resource and its contents: the published criteria (input contract, packet legs, honesty fences, pinned test corpus identity) for the Dispute-Evidence Packet service. The purpose is clear, but it never names its siblings (dispute_packet_precheck / dispute_packet_packet), so the family routing must be inferred from the shared prefix.

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?

"Read these before paying - every packet is reproducible from them" gives an ordering hint (consult criteria before spending), which implies usage. However, it does not state when to skip this tool, nor explicitly route to dispute_packet_precheck or dispute_packet_packet, so the agent must infer the workflow from the naming pattern.

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