Frankfurter

Get exchange rates

get_rates

Read-only

Latest or a single day's exchange rates. The raw-rate companion to convert. With provider, published rates from one or more institutions: on its own base the digits are as published, with the date they took effect.

Input Schema

Name	Required	Description
`base`	No	Base currency or asset code. Default EUR.
`date`	No	Single day YYYY-MM-DD. Omit for the latest rates.
`quotes`	No	Currency or asset codes to return; omit for all.
`provider`	No	Provider key or keys, e.g. ECB or ['ECB', 'HMRC']. Serves published rates instead of the blend; a date inside a weekly, monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/.
`providers`	No	Alias for `provider` accepting multiple provider keys.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 6, 2026
- changedInput schema / properties / base / description
```
Previous value: -"ISO 4217 base currency. Default EUR."New value: +"Base currency or asset code. Default EUR."
```
- removedInput schema / properties / base / maxLength
```
Removed value: -3
```
- removedInput schema / properties / base / minLength
```
Removed value: -3
```
- addedInput schema / properties / base / pattern
```
Added value: +"^[A-Za-z0-9]{3,5}$"
```
- changedInput schema / properties / quotes / description
```
Previous value: -"ISO 4217 quote codes to return; omit for all."New value: +"Currency or asset codes to return; omit for all."
```
- addedInput schema / properties / quotes / items / $ref
```
Added value: +"#/properties/base"
```
- removedInput schema / properties / quotes / items / maxLength
```
Removed value: -3
```
- removedInput schema / properties / quotes / items / minLength
```
Removed value: -3
```
- removedInput schema / properties / quotes / items / type
```
Removed value: -"string"
```

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / provider / description

Previous value: -"Provider key or keys, e.g. ECB or ['ECB', 'HMRC']. Serves published rates instead of the blend; a date inside a monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/."New value: +"Provider key or keys, e.g. ECB or ['ECB', 'HMRC']. Serves published rates instead of the blend; a date inside a weekly, monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/."

Changed6 schema fields changedSep 23, 2026

changedInput schema / properties / provider / description

Previous value: -"Provider key, e.g. UST for U.S. Treasury reporting rates. Serves that institution's published rates instead of the blend; a date inside a monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/."New value: +"Provider key or keys, e.g. ECB or ['ECB', 'HMRC']. Serves published rates instead of the blend; a date inside a monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/."

addedInput schema / properties / provider / items

Added value: +{
+  "maxLength": 8,
+  "minLength": 2,
+  "type": "string"
+}

removedInput schema / properties / provider / maxLength
```
Removed value: -8
```
removedInput schema / properties / provider / minLength
```
Removed value: -2
```
changedInput schema / properties / provider / type
```
Previous value: -"string"New value: +"array"
```

addedInput schema / properties / providers

Added value: +{
+  "description": "Alias for `provider` accepting multiple provider keys.",
+  "items": {
+    "maxLength": 8,
+    "minLength": 2,
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / provider

Added value: +{
+  "description": "Provider key, e.g. UST for U.S. Treasury reporting rates. Serves that institution's published rates instead of the blend; a date inside a monthly or quarterly provider's period returns the rate in force. Keys at https://frankfurter.dev/providers/.",
+  "maxLength": 8,
+  "minLength": 2,
+  "type": "string"
+}

Changed5 schema fields changedJul 27, 2026

changedInput schema / properties / date / description

Previous value: -"Single day YYYY-MM-DD. Mutually exclusive with start/end."New value: +"Single day YYYY-MM-DD. Omit for the latest rates."

removedInput schema / properties / end

Removed value: -{
-  "$ref": "#/properties/date",
-  "description": "Range end YYYY-MM-DD (inclusive). Requires start and quotes."
-}

removedInput schema / properties / providers

Removed value: -{
-  "description": "Provider keys. Omit for blended (default).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedInput schema / properties / quotes / description

Previous value: -"ISO 4217 quote codes. Required when start/end is set."New value: +"ISO 4217 quote codes to return; omit for all."

removedInput schema / properties / start

Removed value: -{
-  "$ref": "#/properties/date",
-  "description": "Range start YYYY-MM-DD (inclusive). Requires end and quotes."
-}

First observedMay 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: provider mode serves published rates instead of the blend, digits are as published on the provider's own base, and a date inside a provider's period returns the rate in force.

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 short sentences, front-loaded with the core purpose and the sibling relationship, with no redundant restatement of the name or schema.

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 5-parameter read-only tool with no output schema, the description covers the non-obvious provider semantics well; the remaining parameters (base, date, quotes) are fully documented in the schema, so nothing critical is missing, though return shape is left implicit.

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 the baseline is 3, but the description adds meaning the schema does not: it clarifies the provider parameter's effect (published rates vs blend, effective-date semantics) and the base-relative digit behavior, which helps an agent interpret results.

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?

States a specific verb and resource ('Latest or a single day's exchange rates') and explicitly positions itself as the 'raw-rate companion to `convert`', so an agent can distinguish it from the conversion sibling 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 Guidelines4/5

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

The 'raw-rate companion to `convert`' framing implies when to prefer this tool (retrieving rates rather than converting), and the provider clause explains the alternative mode. It stops short of an explicit 'use this instead of convert when...' statement or exclusions, so it is clear context but not full routing guidance.

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

All Frankfurter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get exchange rates

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources