Skip to main content
Glama

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

chain_reconcile_criteria

The published criteria for the Chain Reconciliation service (settlement-evidence/v1, multi-hop form): the hop-record shape, the per-hop grading, the ancestor-cap arithmetic, the verdict set, and the pinned public test corpus identity. Read these before paying - every report 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/chain-reconcile/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": "chain_reconcile_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that no payment is required, that there is no x402 challenge, and that this endpoint is free — critical context in a service family built around paid calls. It also gives the HTTP GET equivalent, but says nothing about response size or caching of the criteria document.

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 description is front-loaded with the resource identity and the document contents, then the usage directive, then the payment note and HTTP equivalent. It is dense and slightly run-on with the embedded '- no payment required:' clause, but no sentence is filler.

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

Completeness5/5

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

For a no-parameter, no-output-schema documentation fetch, the description fully covers what the criteria document contains, why to read it, and its payment/auth profile. An agent has everything needed to decide to call it and what it will get back.

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, so there is no parameter meaning to add; baseline 4 applies. The description appropriately spends its words on scope and return content instead of inventing input detail.

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 the exact resource: the published criteria/spec document for the Chain Reconciliation service, and enumerates its contents (hop-record shape, per-hop grading, ancestor-cap arithmetic, verdict set, test corpus identity). This is clearly a spec-retrieval tool rather than the reconcile or precheck actions, though it never explicitly names those siblings, so the differentiation comes mostly from the tool-name convention.

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?

'Read these before paying - every report is reproducible from them' gives a concrete when-to-use trigger tied to the paid downstream tool. It does not explicitly cite chain_reconcile_precheck or chain_reconcile_reconcile by name or state when this tool would be unnecessary, so it falls short of full alternative routing.

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