Skip to main content
Glama

Ecb

by io.github.pipeworx-io

Ecb Exchange Rate

ecb_exchange_rate
Read-onlyIdempotent

AUTHORITATIVE euro foreign-exchange reference rate from the European Central Bank — the official daily EUR spot rate against a target currency (ISO 4217: USD, GBP, JPY, CHF, ...). Use for "current EUR/USD rate", "EURUSD spot", "what is the euro worth in dollars", and for historical FX series. Returns latest ({period, value}) for the current rate plus recent labeled observations; pass start_period/end_period (or last_n) for a longer history. This is the published mid-market reference rate, not a dealer or exchange quote, so there is no bid/ask spread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
last_nNoReturn only the last N observations. Defaults to 30 when no start_period is given.
currencyYesISO 4217 currency code (USD, GBP, JPY, ...)
frequencyNoObservation frequency — D (daily), M (monthly), Q (quarterly), A (annual). Default D.
end_periodNoEnd date (YYYY-MM-DD)
start_periodNoStart date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "currency": "USD"
+  },
+  {
+    "currency": "GBP",
+    "end_period": "2023-12-31",
+    "frequency": "M",
+    "start_period": "2023-01-01"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / last_n
      Added value: +{
+  "description": "Return only the last N observations. Defaults to 30 when no start_period is given.",
+  "type": "number"
+}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: the rate is a published mid-market reference without bid/ask spread. It also specifies the return format (latest with period and value, plus recent observations). This goes beyond what annotations provide.

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?

The description is succinct (3-4 sentences) and front-loaded with the core purpose. Every sentence adds value, and there is no redundant or verbose language.

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?

No output schema exists, but the description explains the return format adequately. It covers main use cases (current rate, historical series) and parameter roles. It could mention error handling or rate limits, but the provided information is sufficient for correct usage.

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 100%, so baseline is 3. The description adds meaning by explaining the default for last_n (30) and the purpose of start_period/end_period for history. This reduces ambiguity beyond the schema descriptions.

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 clearly identifies the tool as providing authoritative EUR reference rates from the ECB, listing example queries and target currencies. It differentiates from sibling tools like ecb_hicp_inflation and ecb_list_dataflows by explicitly focusing on exchange rates.

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?

The description provides explicit use cases ('current EUR/USD rate', 'EURUSD spot', etc.) and explains how to retrieve historical data with start_period/end_period or last_n. It lacks explicit guidance on when not to use this tool or alternatives, but the context is clear enough for an agent.

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

All Ecb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

There is significant overlap between tool clusters: ask_pipeworx_beta is currently functionally identical to ask_pipeworx, and polymarket_arbitrage/polymarket_edges/bet_research all target similar opportunity-discovery tasks. While the descriptions are extremely detailed, the sheer number of similar variants makes it hard to reliably pick the right one.

Naming Consistency4/5

Names are consistently snake_case with meaningful prefixes (ask_, ecb_, polymarket_, pipeworx_) and mostly verb-first structure. Minor deviations like entity_profile and ecb_hicp_inflation are noun-first, but they do not break the overall pattern.

Tool Count2/5

35 tools is well beyond the well-scoped 3–15 range, and the surface feels bloated with redundant meta-tools (ask_pipeworx variants, deep_research, discover_tools, suggest_questions) and peripheral utilities like generate_llms_txt and scan_dependency. Many entries could be consolidated without losing function.

Completeness4/5

For the server's broad data-research domain, coverage is thoughtful and full: query, grounded answer, validation, entity resolution, profiling, comparative analysis, subscription lifecycle, memory, and feedback are all represented. Minor gaps exist (e.g., no direct raw ECB flow browser beyond generic SDMX) but nothing blocking.

Resources