Skip to main content
Glama
Sign In

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

by com.exchangerebel
OverviewDiscussionsAdmin

recoverability_probe_precheck

FREE pre-check (100/day per wallet; pass caller). Returns assessability only - whether the submission is in-policy (URL policy, tool declaration, and ownership attestation all validated). NO probe runs, NO target call is made, and no report is returned. The full signed report is the paid recoverability_probe_probe call.

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": {
      "caller": "<caller>",
      "target_url": "<target_url>",
      "tool_name": "<tool_name>",
      "required_parameter": "<required_parameter>",
      "expected_type": "<expected_type>",
      "valid_arguments": "<valid_arguments>",
      "attestation": "<attestation>"
    },
    "name": "recoverability_probe_precheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
callerYesSolana base58 wallet of the operator; keys the free allowance (100/day per wallet). Free pre-check only.
tool_nameYesName of one tool on the target server (1-128 characters).
target_urlYesThe one target URL of the operator's OWN MCP server (http/https, no embedded credentials; loopback/private/link-local targets are refused). The battery POSTs only to this URL, exactly as submitted.
attestationYesOwnership attestation: operator_wallet, the published attestation statement verbatim, target_url exactly equal to the submission's target_url, battery_id error-recoverability-battery/v1, consent true, attested_at within the past 7 days.
expected_typeYesThe expected type of the required parameter: string, number, integer, boolean, object, or array.
valid_argumentsYesThe operator's own valid arguments for the declared tool; must contain the required parameter with a value of the expected type.
required_parameterYesOne required parameter of the declared tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the rate limit (100/day per wallet, keyed on caller), the three validation dimensions, and explicitly that no target is contacted and no report is returned. It omits what the assessability response actually contains and how failures are surfaced, which is the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the free/quota constraint, then the scope of what is returned, then the paid alternative. Every clause carries distinct information; nothing is padding.

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 seven-parameter tool with a nested attestation object and no output schema or annotations, the description explains the input contract's purpose and what the call does not do. The missing piece is any description of the response shape or failure modes, which matters given there is no output schema.

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 coverage is 100%, so the schema already documents all seven parameters in detail. The description adds only marginal semantics beyond that, mainly that caller keys the free allowance and is pre-check-only — useful but largely a restatement of the schema text.

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 and resource (a free pre-check that returns assessability only) and immediately differentiates it from the sibling recoverability_probe_probe, which produces the signed report. An agent can select between the two without opening either 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?

The free-vs-paid framing plus 'NO probe runs, NO target call is made' gives clear context for when this is the right call, and it names the paid alternative. It stops short of an explicit 'use this first, then call probe' instruction, so the sequencing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana) toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources