Skip to main content
Glama

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

fact_bank_health

Read-onlyIdempotent

FREE fact bank health. Counts only: snapshot_loaded, fact/entity totals, stream labels, store freshness and store_stale flag. — no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/facts/health.

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": "fact_bank_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the tool is free and requires no x402 payment challenge, and it returns aggregates only rather than content. Payment/auth behavior is exactly the kind of thing annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded and short, but the free/no-payment fact is restated four times ('FREE', 'no payment required', 'call directly without payment', 'no x402 challenge', 'this tool is free'), which is redundant waste in an otherwise two-sentence description.

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 read with full annotation coverage and no output schema, the description supplies the metric list, the freshness/staleness signal, and the payment model — everything needed to call it correctly. Only the absence of any guidance versus sibling fact-bank tools keeps it off a 5.

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 the description correctly describes it as a no-input aggregate read. Baseline 4 applies for a 0-param tool; nothing is left ambiguous about what must be supplied.

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 specific resource (fact bank) and enumerates the exact health metrics returned — snapshot_loaded, fact/entity totals, stream labels, freshness, store_stale — plus a scope qualifier ('counts only'). That is more than enough to separate it from fact_bank_catalog or fact_bank_tendency, though it never names those siblings explicitly.

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?

Gives real call guidance about payment ('call directly without payment; no x402 challenge'), which tells the agent it can be invoked with no auth dance. However, it offers no guidance on when to pick this over fact_bank_status or fact_bank_status_preflight, so the tool-selection question is left to inference.

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