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

observatory_precheck

FREE pre-check (100/day per wallet; pass caller). Returns assessability only - whether the catalogue id exists and the window is well-formed; no counts and no grade are returned. The snapshot itself is the paid observatory_snapshot 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>",
      "catalogue_id": "<catalogue_id>",
      "window": "<window>"
    },
    "name": "observatory_precheck"
  }
}

Input Schema

Name	Required	Description
`caller`	Yes	Solana base58 wallet of the operator; keys the free allowance (100/day per wallet).
`window`	Yes	UTC-day window, inclusive: { start: YYYY-MM-DD, end: YYYY-MM-DD }, max 366 days.
`catalogue_id`	Yes	One catalogue id from GET /catalogue (e.g. discovery-total).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It transparently states the cost structure (free, 100/day per wallet), the scope limitations (only assessability), and the data limitations (no counts or grade returned).

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?

The definition is extremely concise. It delivers all critical information—cost, function, limitation, and relationship to other tools—in a single, highly impactful paragraph without any unnecessary jargon.

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?

Given the tool's role as a strategic gateway (pre-check) rather than a pure data retrieval engine, the description is fully complete. It informs the agent exactly what it can and cannot expect from this function call.

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?

While the schema coverage is 100% (meeting the baseline for 3), the description adds critical, meaningful constraints to the parameters. Specifically, it notes the 'caller' wallet allowance and the maximum window length (366 days), adding business context beyond just data types.

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?

The description clearly identifies the tool's purpose as a 'free pre-check' and specifies the exact outcome—returning assessability (catalogue existence and window formation). It explicitly distinguishes its scope from the paid 'observatory_snapshot' call, providing perfect differentiation from potential siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description functions as usage guidance by defining the tool's boundary: it is a free preliminary check, but it is not the final data source. It directly addresses the use case (preliminary check) versus the alternative (the paid snapshot call).

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) tools Inspect

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

Need Help?