Skip to main content
Glama

ECB currency exchange rates and conversion

fx_rates
Read-only

ECB euro foreign exchange reference rates for about 30 currencies, latest or any date since 1999-01-04: base, rate date, rates for the requested currencies, optional converted amounts, and the unmodified ECB euro rates. Rates for non-EUR bases are cross rates calculated by Kit Rx from the ECB euro rates. Daily rates published for information, not transaction quotes. Source: ECB statistics, via the Frankfurter API; the ECB publishes these rates free of charge on its website. Price: $0.002 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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
baseNoISO 4217 code of the base currency; must be one the ECB quotes (about 30 current, e.g. USD, EUR, GBP, JPY, CHF, CNY, INR). Default USD.
dateNoHistorical rate date, YYYY-MM-DD, 1999-01-04 or later. Weekends and TARGET holidays return the latest earlier ECB rates. Omit for the latest rates.
amountNoAmount in the base currency to convert into each symbol: a positive number up to 1e12 with an optional decimal point.
symbolsNoComma-separated ISO 4217 codes to return (up to 50). Omit for every currency the ECB quoted on that date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: it discloses the metered pricing ($0.002 per successful call via x402 v2 in USDC), that failed and empty-result calls are free, the upstream chain (ECB statistics via the Frankfurter API), and the licensing/provenance of the data. It also warns that non-EUR bases are computed cross rates rather than direct ECB quotes, which materially affects interpretation.

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 front-loaded block that leads with the data set and scope before pricing and provenance, so scanning order is sensible. It is dense and the licensing/pricing tail is slightly wordy, but every clause carries information an agent or caller may need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain the response, and it does: base, rate date, per-symbol rates, optional converted amounts, and the unmodified ECB euro rates. Combined with the disclosed cost model, staleness behavior, and cross-rate caveat, an agent has everything needed for a 4-parameter, all-optional tool.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning the schema does not: rate dates are ECB publication dates with weekend/TARGET-holiday carry-forward, and non-EUR `base` values produce Kit Rx-computed cross rates. It also frames the return payload (base, date, rates, converted amounts, raw ECB euro rates) so the agent understands what `amount` and `symbols` produce.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'ECB euro foreign exchange reference rates for about 30 currencies, latest or any date since 1999-01-04', and adds that it also performs conversion. That clearly separates it from sibling price tools such as token_price (crypto) and rx_price (drug pricing).

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?

It establishes the usable scope ('latest or any date since 1999-01-04'), the weekend/holiday fallback, and a when-not caveat ('published for information, not transaction quotes'). It does not name an alternative tool for, say, spot/transaction FX, but the usage envelope is clear enough to select and call it correctly.

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