io.github.mohammad-abbasi-sh/ecb-mcp

ecb_exchange_rates

Retrieve daily ECB euro reference exchange rates for selected ISO currencies, returning current rates and up to 30 days of history.

Instructions

Daily euro reference exchange rates (ECB). currencies: ISO codes like ["USD", "GBP", "JPY"] — default: all major currencies (25). limit: 1..30 days of history per currency (default 5). Returns the latest rate per currency plus history.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`currencies`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the cadence (daily), the data source (ECB), the default currency universe (25 majors), and the shape of the return (latest rate per currency plus history), but says nothing about publication timing, weekend/holiday gaps, rate limits, or authentication.

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 resource and cadence, then parameters, then return shape, in roughly four dense clauses. Slightly telegraphic ('currencies: ISO codes like ...') but no wasted sentences.

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?

Output schema exists, so return-value detail is not required, yet the description still summarizes it. Both optional parameters are documented despite 0% schema coverage. Only minor behavioral gaps (error handling for invalid currency codes, date-gap behavior) remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is doing real work: it defines 'currencies' as ISO codes with a concrete example and a 25-currency default, and bounds 'limit' to 1..30 days with a default of 5. That covers both parameters adequately, but the ISO format is only implied by example rather than stated (no note on case or invalid codes).

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?

States a specific resource and verb-like action: 'Daily euro reference exchange rates (ECB)' with rate-per-currency plus history. The resource is clearly distinct from sibling series such as interest rates, bond yields, and inflation, though the description never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the sibling ECB series tools, and no stated preconditions or exclusions. The only guidance offered is parameter-level defaults (all major currencies, 5 days), which is not usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server