capabilities

Get the official ECB reference exchange rate for a pair (accounting, invoicing, reporting)

fx_reference_rate

Read-onlyIdempotent

European Central Bank euro foreign exchange reference rate for a pair - the official daily fix used for accounting, invoicing and reporting - latest or any date in the last 90 days. The ECB publishes EUR/XXX only, so inverse and cross rates are computed from the same fix and named in rate_derivation. Use when: Convert or report an amount at an official daily rate both sides of a contract can verify against the ECB. Not for: You need an executable, tradable, live or intraday market rate - this is a daily fix only. Price: USD 0.002/call (x402), 0.0015 (account key).

Input Schema

TableJSON Schema

Name	Required	Description
`base`	Yes	ISO 4217 code of the base currency. EUR is always available; other currencies must be in the ECB reference rate list for the selected date.
`date`	No	Optional ISO calendar date (YYYY-MM-DD) within the last 90 days. When the ECB published no fix on that date (a TARGET closing day), the latest prior fix is returned with a note.
`quote`	Yes	ISO 4217 code of the quote currency. EUR is always available; other currencies must be in the ECB reference rate list for the selected date.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/fx.reference_rate
`meta`	Yes

Schema Changelog

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

Changed7 schema fields changedAug 18, 2026

removedOutput schema / properties / data / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / data / description

Added value: +"Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/fx.reference_rate"

removedOutput schema / properties / data / properties

Removed value: -{
-  "attribution": {
-    "description": "Required attribution text - always the exact string \"Source: European Central Bank\".",
-    "type": "string"
-  },
-  "base": {
-    "description": "Base currency (ISO 4217, upper case).",
-    "type": "string"
-  },
-  "disclaimer": {
-    "description": "Plain-language statement of what this rate is and is not, including that it must not be relied on for settlement or dealing and that the same content is available free of charge from the ECB website. When the rate is inverted or crossed it also states that Eckari computed it from the ECB fix - the ECB requires its information to be reproduced accurately and any modification to be stated.",
-    "type": "string"
-  },
-  "is_derived_cross": {
-    "description": "True when neither side is EUR, so the rate is a cross computed by Eckari from two euro reference rates of the same fix. False for a plain inverted pair such as USD to EUR - read is_inverted for that case.",
-    "type": "boolean"
-  },
-  "is_inverted": {
-    "description": "True whenever base is not EUR. The ECB publishes units of currency per 1 EUR only, so the published quotation for the base currency is inverted (divided into) to produce this rate - the value is computed by Eckari, not published by the ECB. False only when base is EUR.",
-    "type": "boolean"
-  },
-  "note": {
-    "description": "Set when the fix returned is not the one asked for - either the requested date had no fix and the latest prior fix was returned, or no fix has been published for today (UTC) yet and the latest published fix was returned.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "published_pair": {
-    "description": "The single ECB-published quotation this rate comes from, always in the form EUR/XXX - for EUR to USD the rate is that quotation, and for USD to EUR it is its reciprocal. Null when no single published quotation gives the rate - a cross (rate_derivation cross) or the EUR to EUR identity; see published_pairs_used for every quotation involved.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "published_pairs_used": {
-    "description": "Every ECB quotation used to produce the rate, in the form EUR/XXX - two for a cross, one for published or inverse, none for the identity.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "quote": {
-    "description": "Quote currency (ISO 4217, upper case).",
-    "type": "string"
-  },
-  "rate": {
-    "description": "Units of quote currency per 1 unit of base currency, as a decimal string with 6 decimal places. Computed with exact integer arithmetic from the ECB fix (rate = published(quote) / published(base), with EUR = 1) and rounded half-even - never floating point. When is_inverted or is_derived_cross is true this is a computed value, not a figure published by the ECB, and rounding means it need not round-trip exactly against the published fix.",
-    "pattern": "^[0-9]+\\.[0-9]{6}$",
-    "type": "string"
-  },
-  "rate_date": {
-    "description": "TARGET working day of the ECB fix used (the Cube time value), which may be earlier than a requested date or than today when no fix has been published yet - see note.",
-    "type": "string"
-  },
-  "rate_derivation": {
-    "description": "How the rate relates to what the ECB publishes. published = the ECB EUR/quote fix itself (base EUR); inverse = 1 divided by the EUR/base fix (quote EUR), an Eckari computation; cross = the EUR/quote fix divided by the EUR/base fix, an Eckari computation from two published quotations of the same fix (neither side EUR); identity = EUR to EUR (1). Only published values are ECB figures.",
-    "enum": [
-      "published",
-      "inverse",
-      "cross",
-      "identity"
-    ],
-    "type": "string"
-  },
-  "rate_kind": {
-    "description": "Always the string reference - an official daily reference rate, not a tradable or executable market rate.",
-    "type": "string"
-  },
-  "source": {
-    "description": "Always the string ecb.",
-    "type": "string"
-  }
-}

removedOutput schema / properties / data / required

Removed value: -[
-  "base",
-  "quote",
-  "rate",
-  "rate_date",
-  "source",
-  "rate_kind",
-  "is_inverted",
-  "is_derived_cross",
-  "rate_derivation",
-  "published_pair",
-  "published_pairs_used",
-  "attribution",
-  "disclaimer"
-]

addedOutput schema / properties / meta / properties / attribution_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / retrieved_at / format
```
Added value: +"date-time"
```

addedOutput schema / properties / meta / required

Added value: +[
+  "capability",
+  "version",
+  "retrieved_at",
+  "source",
+  "freshness",
+  "request_id"
+]

First observedAug 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false. The description adds that the rate covers latest or any date in the last 90 days, that ECB publishes EUR/XXX only with derived rates named in rate_derivation, and mentions pricing. It also notes date fallback to prior fix on non-publishing days. This adds behavioral context beyond the annotations.

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?

Description is a few sentences but each adds value: purpose, limitation (EUR/XXX only), usage guidance, pricing. It front-loads the main purpose. Could be slightly tighter, but no fluff.

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?

Given three parameters and existence of output schema, the description covers purpose, usage, behavioral details, limitations, and pricing. It is complete for an agent to select and invoke correctly without further clarification.

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% with descriptions for base, quote, and date. The description adds semantic value: explains that EUR/XXX is the native fix (inverse/cross computed) and that date returns latest prior fix if no ECB fix on that day. This goes beyond the schema's 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 states it returns 'European Central Bank euro foreign exchange reference rate' for a pair, specifying it's the official daily fix for accounting, invoicing, and reporting. It distinguishes itself from live/tradable rates and mentions that inverse/cross rates are computed, giving a precise scope.

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?

Explicit 'Use when' and 'Not for' sections: use for official daily rates verifiable against ECB, not for executable/live/intraday rates. This provides clear context for when to invoke this tool versus alternatives like live rate APIs.

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

All capabilities tools Inspect

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

A4.4/5.0

Disambiguation4/5

Tools are largely distinct, targeting specific entities (UK company, US company, domain, LEI, FX, location, parcel, weather) or sub-aspects (e.g., accounts vs. charges vs. directors). Overlap exists between company.uk.profile and company.uk.status (both contain status info, but the latter is cheaper and focused). Also, company.uk.filings and company.us.filings_latest could be confused if an agent generalizes 'filings' across jurisdictions.

Naming Consistency5/5

All tools follow a consistent pattern: domain_entity_subject (e.g., company_uk_accounts, domain_expiry, weather_us_alerts). Underscores and lower case are used throughout. Verbs are implied by the noun (e.g., 'search' for lookup, 'detect' for identification). No mixed conventions or unpredictable names.

Tool Count4/5

24 tools is on the high side but still reasonable for a general-purpose data server spanning multiple domains (company, domain, entity, fx, location, parcel, weather). Each domain gets a cohesive set, and the documentation justifies each tool. Could be slightly leaner if some niche tools (e.g., domain_expiry vs. registration) were merged, but overall scoping is acceptable.

Completeness4/5

Each domain offers good coverage: UK company tools cover CRUD-like operations (profile, status, search, filings, charges, directors, owners, registered office); similarly for US companies (profile, filings, resolve, latest filings). Weather has forecast, observation, alerts. Parcel only detects carrier (no tracking). Missing features like advanced filtering on company filings or less common domains, but core workflows are covered.

Resources

Need Help?