Skip to main content
Glama

Markets and macro (x402)

fx_rates

$0.002 via x402: All ECB reference rates for the latest day, rebased to a base currency (EUR by default; any of the 30 currencies): {base, date, rates:{USD:..., JPY:...}}. Pay 0.002 USDC through https://store.agentexchange.work/gw/fx/rates?base=USD. Via the Agent Exchange store gateway; settled by Coinbase.

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": "fx_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo3-letter code, default EUR
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses the paid x402 model, the exact cost (0.002 USDC), the gateway URL, and the key behavior that x_payment omission returns the price rather than data. It omits rate-limit or settlement-time details, but the paywall behavior is well 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?

Dense but front-loaded with the essential cost and resource, and every sentence carries content (scope, cost, currency count, return shape, payment path). The leading price tag is slightly awkward as an opener but is informative rather than wasteful.

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 simple 2-parameter tool with no output schema, the description supplies the return shape {base, date, rates:{...}} and the complete payment flow. It lacks only usage routing against fx_convert/fx_history.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning: it clarifies 'any of the 30 currencies' for base and explains the x_payment parameter's dual behavior (paid data vs. price quote when absent), which the schema alone does not convey.

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 and scope: 'All ECB reference rates for the latest day, rebased to a base currency.' The 'latest day' framing implicitly distinguishes it from fx_history, and 'rates' distinguishes it from fx_convert, though no sibling is explicitly named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use this versus fx_convert or fx_history, nor any preconditions beyond payment. It explains the payment mechanics but offers no routing guidance for the agent among the closely related fx_* siblings.

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