Get ECB exchange rates for EUR against major currencies, or ECB key interest rates (ESTR). Returns live rates from the European Central Bank Statistical Data Warehouse.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | fx (exchange rates, default) or rates (interest rates) | fx |
| currencies | No | Comma-separated currency codes (default: USD,GBP,JPY,CHF,CNY) | USD,GBP,JPY,CHF,CNY |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Mentions 'live rates' and the data source but does not elaborate on behavioral traits such as authentication needs, rate limits, or whether the operation is safe (though reading is implied). With no annotations, the description carries the burden but only minimally addresses it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence covering the tool's purpose and data source. Concise and to the point, though could be slightly more structured with separation of modes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does not explain the return format or structure of the rates. While it covers the two modes and default currencies, it omits important context like the base currency (EUR) being fixed and the data source details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters already explained in the schema. The description merely repeats the schema text, adding no additional semantic value beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it gets ECB exchange rates for EUR against major currencies or key interest rates, specifying the source (ECB Statistical Data Warehouse). Distinguishes from sibling tools which are different data sources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for fetching ECB rates but provides no explicit guidance on when to use versus alternatives like get_eurostat_data or get_money_supply, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct category of European economic data: ECB exchange rates and interest rates, Eurostat statistics, and ECB monetary data. Descriptions clearly differentiate them, preventing confusion.
All three tools use a consistent 'get_' prefix followed by descriptive snake_case names (e.g., get_ecb_rates, get_eurostat_data), forming a predictable pattern.
With only 3 tools, the server is tightly scoped to European economic data. Each tool serves a clear purpose without unnecessary bloat, making it easy for agents to navigate.
The tool set covers key areas: exchange rates, macroeconomic indicators (GDP, inflation, unemployment), and monetary aggregates. Minor gaps exist (e.g., no tool for bond yields or historical exchange rate ranges), but core needs are met.