Skip to main content
Glama

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

funding_check_criteria

The published criteria for the Funding Check service (payer-preflight/v1, op funding-check): what readiness means per network, the fee-coverage rules, 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/funding-check/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": "funding_check_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 usefully discloses that no payment is required, there is no x402 challenge, the tool is free, and the HTTP equivalent is a GET endpoint. It does not explicitly state read-only behavior or response format, but the key access behavior is covered.

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 core purpose and content of the criteria. The payment-free access note is somewhat repetitive across 'no payment required,' 'without payment,' 'no x402 challenge,' and 'free,' but it remains short and scannable.

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 zero-parameter, annotation-free criteria retrieval tool with no output schema, the description is complete enough: it states what the criteria cover, why to read them, and how to access the tool without payment. Nothing essential for correct invocation appears missing.

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 has zero parameters, so there is no parameter semantics to clarify. The description does not need to add parameter meaning beyond the empty schema, and the baseline for a no-parameter tool is 4.

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 precisely identifies the artifact returned: the published criteria for the Funding Check service, including readiness semantics per network, fee-coverage rules, and the pinned test corpus identity. This clearly distinguishes the documentation/criteria tool from the sibling check and precheck tools.

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?

It gives clear timing guidance: 'Read these before paying,' and explains that reports are reproducible from the criteria. It does not explicitly name the sibling check or precheck tools as alternatives, but the intended usage context is clear for a criteria-retrieval tool.

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