YourAITools MCP Hub

FXRate: Convert an amount between currencies (ECB rates)

convert_currency

Read-onlyIdempotent

Convert an amount between two currencies at the official ECB reference rate (latest or a past date). Inputs: from, to (ISO codes like USD, EUR, JPY), amount (default 1), date (optional YYYY-MM-DD). Returns rate, result, inverse_rate and the rate date. Free: 30 calls/day per IP, then $0.001 per call via x402 or credits.

[FXRate via YourAITools MCP Hub] Free tier: same as FXRate's own MCP server (call without payment and without tier). Paid: convert $0.001 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "convert_currency"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	To currency: ISO 4217 code, e.g. USD, EUR, GBP, JPY (31 supported)
`date`	No	Optional YYYY-MM-DD (default: latest). Weekends/holidays use the previous ECB rate.
`from`	Yes	From currency: ISO 4217 code, e.g. USD, EUR, GBP, JPY (31 supported)
`tier`	No	Paid tier: convert $0.001. Omit tier (with no credits key or x402 payment) to use the free tier.
`amount`	No	Amount to convert (default 1), up to 1e15

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 30, 2026
- addedInput schema / properties / amount / examples
```
Added value: +[
+  100
+]
```
- addedInput schema / properties / from / examples
```
Added value: +[
+  "USD"
+]
```
- addedInput schema / properties / to / examples
```
Added value: +[
+  "EUR"
+]
```
AddedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond that: ECB rate source, weekend/holiday fallback, return fields, free-tier limits, paid pricing, auth options, and refund behavior for failed calls.

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 inputs are front-loaded and efficient. The second paragraph is dense with hub/payment boilerplate, but it remains relevant to invocation and is not padded with extraneous marketing.

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?

For a tool without an output schema, the description explains the return values (rate, result, inverse_rate, rate date), date behavior, required inputs, defaults, and payment/auth implications. An agent has enough information to call it correctly.

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 parameters, including ISO codes, default amount, date format, and the paid tier enum. The description repeats some of this but adds little semantic detail beyond the schema.

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 states a specific verb and resource: convert an amount between two currencies at the ECB reference rate. It also specifies latest vs. past date and lists inputs and outputs, making it clearly distinct from rate-listing siblings like fx_rates and fx_history.

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?

It gives clear context for when to use it: converting an amount, optionally at a historical ECB rate. It does not explicitly say when to prefer fx_rates or fx_history instead, but the conversion framing makes the intended use obvious.

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?