Skip to main content
Glama

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

rail_router_criteria

The published criteria for the Rail Router service (payer-preflight/v1, op rail-router): the rail grammar for each x402 form, the disclosed MPP-signals construction, 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/rail-router/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": "rail_router_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it states that no payment is required, that there is no x402 challenge, that the call is free, and that outputs are reproducible from the published corpus. It also gives the HTTP equivalent endpoint. It does not describe response shape or size, which keeps it from a 5.

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 purpose is front-loaded in the first sentence, followed by the when-to-use cue and the free-call clarification. It is dense with domain jargon (x402, MPP-signals) but each clause adds information rather than repeating structured fields.

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-only tool with no output schema, the description supplies what the document contains, why to read it, that it is free, and where the HTTP equivalent lives. Only the return format and volume are unaddressed, which is a minor gap for a criteria-document endpoint.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly signals a no-argument call by framing it as a direct read.

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 (the published criteria for the Rail Router service) and enumerates its contents: rail grammar per x402 form, MPP-signals construction, and pinned test corpus identity. That is far more specific than a restatement of the name. It stops short of explicitly contrasting itself with rail_router_precheck or rail_router_route, so sibling differentiation is left to the naming convention.

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?

"Read these before paying" gives a clear timing cue tied to the paid route sibling, and "every report is reproducible from them" implies why. However, no sibling is named and there is no explicit statement of when this is unnecessary or how it relates to rail_router_precheck, so the agent must infer the workflow.

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