YourAITools MCP Hub

FXRate: Daily exchange-rate history for a currency pair

fx_history

Read-onlyIdempotent

Daily ECB reference rates for one currency pair between start and end (max 366 days), with first, last, min, max and percent change. Free: 30 calls/day per IP, then $0.002 per call.

[FXRate via YourAITools MCP Hub] Free tier: same as FXRate's own MCP server (call without payment and without tier). Paid: history $0.002 per call, with a credits key (Authorization: Bearer yatc_...) or x402 (USDC; the hub returns the payment terms). Failed tool calls aren't charged: credits are refunded automatically and x402 payments only settle on success.

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

Input Schema

Name	Required	Description
`end`	No	YYYY-MM-DD end date (default: today); max 366 days after start
`base`	Yes	Base currency: ISO 4217 code, e.g. USD, EUR, GBP, JPY (31 supported)
`tier`	No	Paid tier: history $0.002. Omit tier (with no credits key or x402 payment) to use the free tier.
`quote`	Yes	Quote currency: ISO 4217 code, e.g. USD, EUR, GBP, JPY (31 supported)
`start`	Yes	YYYY-MM-DD start date

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026
- addedInput schema / properties / base / examples
```
Added value: +[
+  "EUR"
+]
```
- addedInput schema / properties / end / examples
```
Added value: +[
+  "2026-10-29"
+]
```
- addedInput schema / properties / quote / examples
```
Added value: +[
+  "USD"
+]
```
- addedInput schema / properties / start / examples
```
Added value: +[
+  "2026-10-01"
+]
```
AddedOct 25, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: ECB as source, response aggregates (first/last/min/max/percent change), free-tier limit of 30 calls/day, paid pricing, accepted auth schemes (Bearer credits key or x402), and the failed-call refund policy. This is rich behavioral disclosure.

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 core purpose and constraints lead, with pricing and payment mechanics following. The payment/auth boilerplate is somewhat verbose but each block carries actionable information for an agent deciding whether it can call the tool.

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?

With no output schema, the description helpfully names the returned aggregates and covers the data source, date limits, rate limits, and auth. A minor gap is that ECB business-day behavior (missing weekends/holidays) is not mentioned, and output format details (e.g., per-day series) remain unstated.

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 base, quote, start, end, and tier semantics are already documented in the schema. The description's mention of the 366-day maximum and pricing for tier adds only marginal value beyond that baseline.

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?

States a specific verb and resource: daily ECB reference rates for one currency pair over a date range, plus the aggregates returned. It is clear without opening the schema. It does not explicitly distinguish itself from siblings like fx_rates or convert_currency, so it falls short of a 5.

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?

The ECB data source and 366-day cap imply when the tool fits, but the description never states when to prefer this over fx_rates (current rates) or convert_currency (single conversion). Usage is inferable rather than explicit.

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

All YourAITools MCP Hub tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?