Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

fiat-rates

[x402 paid: $0.003 USDC on Base] Live fiat FX rates vs USD (EUR, GBP, RUB, CNY, JPY... ?pairs=EUR,RUB). tools/call returns the live payment challenge.

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": "fiat-rates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does well: it discloses a paid x402 flow, the exact price ($0.003 USDC on Base), and that tools/call returns the live payment challenge. It omits refresh cadence, rate limits, and whether repeated calls re-charge, 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?

A single dense sentence that front-loads the payment requirement and price before the data description. Every element earns its place, though the parenthetical currency list is slightly compressed with an ellipsis.

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-output-schema tool the description covers purpose, cost, network, and the challenge-based invocation result. The only real gap is how a caller completes payment after receiving the challenge, which is likely handled by the client rather than the description.

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 schema declares zero properties, so the baseline is 4. The description adds a '?pairs=' usage hint beyond the empty schema, though the fact that this argument is absent from the schema creates minor ambiguity about how it should 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 (live fiat FX rates vs USD) with example currencies, so an agent knows exactly what it retrieves. It does not name or differentiate itself from plausible siblings like coin-convert or crypto-price, leaving a little routing ambiguity.

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?

Usage is only implied: the tool is for live fiat FX against USD, and the '?pairs=EUR,RUB' fragment hints at filtering. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative for conversion or crypto rates.

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