Skip to main content
Glama

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

facilitator_fit_criteria

The published criteria for the Facilitator Fit service (payer-preflight/v1, op facilitator-fit): the fit states, the factor list, the guarantee absence rule, 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/facilitator-fit/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": "facilitator_fit_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and it does disclose the cost model ('no payment required... no x402 challenge; this tool is free') and the reproducibility guarantee, which are genuinely useful. It omits the return shape beyond a content inventory, and does not state read-only/static-ness or response size, leaving real gaps for a zero-parameter tool.

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 content inventory is front-loaded and each clause carries information. The single dash-chained sentence is somewhat run-on and the free/payment note is repeated in effect ('before paying' and 'no payment required'), costing minor economy.

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?

There is no output schema, and the description compensates by enumerating what the criteria document contains (fit states, factors, guarantee absence rule, corpus identity). For a static zero-param reference tool this is close to sufficient; only the concrete response format and size remain unstated.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description adds the HTTP equivalent GET URL, which is useful context even though not parameter semantics.

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 a specific resource and enumerates its contents: fit states, factor list, guarantee absence rule, and pinned public test corpus identity, plus the service/op identity (payer-preflight/v1, op facilitator-fit). That is far more than a restatement of the name. It does not explicitly name the facilitator_fit_check or facilitator_fit_precheck siblings, so differentiation relies on the reader inferring the _criteria vs _check 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 clear ordering constraint: consult this before invoking the paid check flow. It stops short of explicitly excluding cases or naming the alternative tools that consume these criteria, so an agent must infer which sibling to run afterward.

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