Skip to main content
Glama

Eu fx history

eu_fx_history
Read-onlyIdempotent

Use for a short euro exchange rate history: daily ECB reference rates of one currency against EUR for up to the last 30 days, with min, max, mean and percent change. Returns the paid x402 request for your input (GET /eu/fx/history, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One currency, up to 30 days; for the latest rates of all currencies use eu_fx. First call each day returns the data itself, free; later calls return the paid request.

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_fx_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccyNoISO 4217 code of the currency quoted against EUR, e.g. USD, GBP, JPY; one of the currencies the ECB publishesUSD
daysNocalendar days back from the latest ECB publication, default 30 (out-of-range values are clamped); fewer rows than days because the ECB publishes on TARGET working days only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ccy / description
      Previous value: -"ISO 4217 code of the currency quoted against EUR, e.g. USD, GBP, JPY; must be one the ECB publishes"New value: +"ISO 4217 code of the currency quoted against EUR, e.g. USD, GBP, JPY; one of the currencies the ECB publishes"
  2. Changed2 schema fields changed
    • changedInput schema / properties / ccy / description
      Previous value: -"ISO 4217 currency quoted against EUR, e.g. USD, GBP, JPY"New value: +"ISO 4217 code of the currency quoted against EUR, e.g. USD, GBP, JPY; must be one the ECB publishes"
    • changedInput schema / properties / days / description
      Previous value: -"calendar days back from the latest ECB publication"New value: +"calendar days back from the latest ECB publication, default 30 (out-of-range values are clamped); fewer rows than days because the ECB publishes on TARGET working days only"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish a safe read, but the description adds the real cost of calling it: $0.002 per call, bad input refused before any charge, first call each day free, later calls returning the paid request. It also discloses the unusual call pattern (GET the returned URL with an x402 or MPP client), which no annotation conveys.

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?

The scope and the sibling routing come first, then the payment and call mechanics, so the definition is well-ordered. The payment flow takes several sentences and could be compressed, but each sentence conveys something the agent does not already know.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description covers the return values (min, max, mean, percent change), the payment mechanism, the free-then-paid behavior, and validation before charge. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the pattern, default, and clamping behavior for ccy and days are already documented. The description only restates the aggregate constraint "One currency, up to 30 days" and adds no syntax or edge-case detail beyond the schema. It meets the baseline without adding much extra value.

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?

The description names a specific verb and resource: "daily ECB reference rates of one currency against EUR for up to the last 30 days, with min, max, mean and percent change". It also scopes the tool against its sibling, stating "for the latest rates of all currencies use eu_fx", so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

It states the exact conditions that select this tool (one currency, up to 30 days) and names the alternative (eu_fx) with the condition that selects it (latest rates of all currencies). The exclusions are explicit rather than implied.

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