Skip to main content
Glama

Get ECB exchange rate

get_exchange_rate
Read-onlyIdempotent

Returns the European Central Bank's euro reference rate for a currency on a given date (or the last rate before it, on weekends and holidays), and optionally converts an amount to or from euro. Use it for invoices in foreign currency.

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": {
      "currency": "<currency>"
    },
    "name": "get_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD, e.g. the invoice date. Default: today.
amountNoOptional amount to convert.
currencyYesThree-letter currency code, e.g. CHF, USD, CZK.
directionNoto_eur (default): the amount is in the currency and is converted to euro. from_eur: the amount is in euro.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail by explaining the weekend/holiday fallback to the last available rate and the optional conversion behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences: the core behavior is front-loaded, and the invoice use case follows naturally. There is no redundant or filler wording.

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 read-only rate lookup with an input schema that fully documents its parameters, the description covers purpose, fallback behavior, conversion, and intended use. It does not fully specify the return shape when conversion is requested, but no output schema exists and the description remains sufficient to call the tool correctly.

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 schema already documents all five parameters. The description adds meaning beyond the schema by clarifying that the date may fall back to the last prior rate on weekends and holidays and that the optional amount can be converted to or from euro.

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 a specific verb and resource: it returns the European Central Bank's euro reference rate for a currency on a given date, with optional conversion. This is clear and unambiguous, though it does not explicitly differentiate the tool from any sibling alternatives.

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?

The description gives a clear use context: 'Use it for invoices in foreign currency.' It does not state when not to use the tool or name alternative tools, but the intended scenario is explicit enough for an agent to select it appropriately.

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