Skip to main content
Glama

Currency exchange rate

exchange_rate
Read-only

Convert between currencies at European Central Bank reference rates (30 currencies), for the latest business day or any day in the last 90. These rates are published free by the ECB at ecb.europa.eu and are for information only, not for transactions.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need to convert between currencies at an official reference rate. Parameters: from and to: 3-letter codes (30 supported). amount: default 1. date: YYYY-MM-DD within the last 90 days; leave out for the latest business day. Returns: the rate, the converted amount and the ECB date used. For information, not for transactions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes3-letter currency code, e.g. "EUR".
dateNoYYYY-MM-DD within the last 90 days.
fromYes3-letter currency code, e.g. "USD".
amountNoAmount to convert (default 1).
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / amount / description
      Added value: +"Amount to convert (default 1)."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses cost ($0.002 USDC per call over x402), that failed calls are free, the quote-then-sign payment handshake, and the data provenance/disclaimer. These are exactly the behavioral traits an agent cannot infer from the annotations.

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?

Front-loaded with the core capability and logically ordered (what it does, cost, when to use, parameters, returns). Slightly redundant: 'for information only, not for transactions' appears twice, and the payment mechanics repeat what the payment parameter already documents.

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?

No output schema exists, and the description compensates by describing the return values (rate, converted amount, ECB date used). Remaining minor gap: the 30 supported currencies are never listed, so an agent can still pick an unsupported code, and nothing describes error behavior beyond the free-failure pricing note.

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 100%, so the baseline is 3, but the description adds real meaning: from/to must be among 30 supported 3-letter codes, amount defaults to 1, and omitting date yields the latest business day. The 90-day date constraint is also restated in behavioral terms rather than just a format hint.

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?

States a specific verb and resource (convert between currencies) plus the authoritative source (ECB reference rates), the coverage (30 currencies), and the time window (latest business day or any day in the last 90). No sibling tool in the list does FX conversion, and the description makes that scope unmistakable.

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?

Includes an explicit 'When to use' line and a clear exclusion ('for information, not for transactions'). It does not name an alternative tool for transactional FX, but no sibling offers one, so the routing context is effectively complete.

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.