Skip to main content
Glama

fx_history

Retrieve ECB reference-rate history for one currency pair or up to 10 targets over a date range up to 2 years, with daily points and summary statistics.

Instructions

Official ECB reference-rate time series for a currency pair (or up to 10 targets) over a date range up to 2 years: daily points plus first/last/min/max/mean/% change. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "to": "<to>",
      "start": "<start>"
    },
    "name": "fx_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget(s), comma-separated
endNoYYYY-MM-DD, default today
fromNoBase ISO 4217, default EUR
startYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses per-call pricing (0.002 USDC on Base), the payment protocol (x402), and the exact failure mode without a payment key (returns the 402 challenge). It does not cover retry/refund semantics, rate limits, or how gaps (weekends/holidays with no ECB fixing) appear in the series.

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?

Three tight sentences, front-loaded with the data scope, followed by return contents and then the billing/error condition. No filler and no repetition of the schema's field descriptions.

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 tool with no annotations and no output schema, the description covers the essentials: what data is returned, size limits, cost, and the 402 behavior. The remaining gap is the shape of the actual response payload (per-target nesting, unavailable-day handling), which matters for a multi-target, multi-day series but is not addressed.

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 100%, so the schema already documents all four parameters, making 3 the baseline. The description adds real constraints not present in the schema — a maximum of 10 comma-separated targets and a maximum 2-year span — but says nothing about date format edge cases or inclusive/exclusive range behavior beyond what the schema states.

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 first clause names a specific resource and scope: 'Official ECB reference-rate time series for a currency pair (or up to 10 targets) over a date range up to 2 years.' It also enumerates the returned statistics (daily points plus first/last/min/max/mean/% change), so the agent knows exactly what data comes back. It stops short of naming the sibling `fx` as the alternative for a single spot rate, so differentiation is left implicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'time series ... over a date range' signals historical/multi-day retrieval versus a point lookup, and the cost note implies it should not be called casually. There is no explicit 'use this instead of X' or exclusion such as 'do not use for a single latest rate.'

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