Skip to main content
Glama

Factline KYC, KYB and agent payments

ECB exchange rates (free)

eu_exchange_rates
Read-onlyIdempotent

Free. Use when the user needs an official euro exchange rate or a conversion for an invoice, contract or report: ECB euro reference rates (about 30 currencies), today or any working day in the last 90 days, with cross rates. Input: base (default EUR), symbols (e.g. USD,GBP), optional date YYYY-MM-DD and amount.

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

Input Schema

NameRequiredDescriptionDefault
baseNo
dateNo
amountNo
symbolsNo

Output Schema

NameRequiredDescriptionDefault
baseNoBase currency
dateNoECB reference date
ratesNoRates per currency
sourceNoSources to cite

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "base": {
      +      "description": "Base currency"
      +    },
      +    "date": {
      +      "description": "ECB reference date"
      +    },
      +    "rates": {
      +      "description": "Rates per currency"
      +    },
      +    "source": {
      +      "description": "Sources to cite"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds genuinely non-redundant context: 90-day lookback, official ECB source, ~30 currencies, cross-rate support, and that it is free — details that would otherwise become trial-and-error.

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-loads 'Free' and the usage trigger, then packs source, coverage, window and input formats into one dense paragraph. Every clause carries information; no padding or repetition.

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?

A simple lookup tool with an output schema and complete annotations; the description supplies the lookback window, date format, defaults and cross-rate capability. An agent has enough to call it confidently, with only minor ambiguity around the amount parameter's effect on the response.

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 0%, so the description must carry the parameter burden, and it does: base defaults to EUR, symbols are comma-separated codes (USD,GBP), date format YYYY-MM-DD, plus an amount for conversions. It does not explicitly say what 'amount' affects (returned converted value vs. raw rate), which is the remaining gap.

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 resource (ECB euro reference rates) and scope (today or any working day in the last 90 days, ~30 currencies, cross rates). No sibling in the list covers exchange rates, and the description makes the retrieval/conversion purpose unambiguous.

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?

Gives a clear trigger: 'Use when the user needs an official euro exchange rate or a conversion for an invoice, contract or report.' No alternatives are named, but none exist among the siblings, so the only gap is the absence of explicit exclusions.

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