Skip to main content
Glama

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

quote_registry_criteria

The published criteria for the Quote Registry service (quote-registry/v1): the listing fields, the per-field free validation reasons, duplicate handling, the query states, the caps, and the pinned public test corpus identity. - no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/quote-registry/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": "quote_registry_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 must carry the behavioral load, and it discloses the two things that matter most here: no payment is required and no x402 challenge is issued, and the operation maps to a plain HTTP GET (implying a static, side-effect-free read). The gap is that it does not describe the response shape or size, which matters since no output schema exists.

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 and the enumerated content are front-loaded in the first sentence, with the payment note and HTTP equivalent appended as supporting detail. The stray leading dash in '- no payment required' reads like a malformed bullet left over from templating, and the parenthetical '(quote-registry/v1)' plus URL are both compact and useful, so waste is minor.

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, no-side-effect spec-fetch tool, the description covers what is returned (by section), the payment model, and the HTTP analogue. The missing piece is the return format/serialization, which is not covered by any output schema — the content enumeration compensates for most, but not all, of that gap.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly makes no attempt to describe inputs and instead spends its words on return content.

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 states precisely what the tool returns: the published Quote Registry (quote-registry/v1) criteria, enumerated as listing fields, per-field validation reasons, duplicate handling, query states, caps, and test corpus identity. That is a specific resource with concrete content, but it never distinguishes itself from sibling tools like quote_registry_list, quote_registry_query, or quote_diff_criteria, leaving the agent to infer that '_criteria' means 'fetch the spec' rather than 'fetch data'.

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?

It gives one strong operational instruction — call directly, no payment/x402 challenge required — which is real invocation guidance in a paid-tool ecosystem. However, it never says when to call this instead of quote_registry_list or quote_registry_query, nor does it state any prerequisite (e.g., fetch criteria before interpreting listings). Usage is implied by the content list rather than declared.

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