OnlineCyberTools MCP (280+ filterable tools)

math_currency_converter_convert

Convert a money amount from one ISO 4217 currency to another using daily end-of-day forex rates. Returns converted result, applied rate, and rate date.

Instructions

Currency Converter. Convert a money amount from one ISO 4217 currency to another using daily end-of-day (EOD) FX rates. Returns success plus a data object with the converted result, the applied rate and its inverse, the rate date, and the resolution path (direct, triangulation through USD, or identity). Rates come from a local cache of EODHD daily forex data; a first-time or stale currency pair triggers an on-demand outbound fetch from EODHD, so results change day to day and the call is not idempotent. Use this for present-day conversion between the 31 supported currencies; use math_currency_converter_history for a multi-day close-price series for charting, and math_unit_converter for non-currency length/mass/volume/speed conversion. Rate-limited (30 req/min anonymous) to protect the upstream API quota.

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": "math_currency_converter_convert"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Source ISO 4217 currency code (3 letters, case-insensitive). Must be one of the 31 supported codes.
`to`	Yes	Target ISO 4217 currency code (3 letters, case-insensitive). Same 31-code enum as from; equal from/to returns a rate of 1.
`amount`	No	Amount in the source currency to convert. Must be a finite number; defaults to 1 when omitted.

Output Schema

Name	Required	Description	Default
`success`	No	True when the conversion succeeded.
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / amount / default
```
Added value: +1
```

addedInput schema / properties / amount / description

Added value: +"Amount in the source currency to convert. Must be a finite number; defaults to 1 when omitted."

addedInput schema / properties / amount / minimum
```
Added value: +0
```

changedInput schema / properties / amount / type

Previous value: -"integer"New value: +"number"

addedInput schema / properties / from / description

Added value: +"Source ISO 4217 currency code (3 letters, case-insensitive). Must be one of the 31 supported codes."

addedInput schema / properties / from / enum

Added value: +[
+  "USD",
+  "EUR",
+  "GBP",
+  "JPY",
+  "CHF",
+  "CAD",
+  "AUD",
+  "NZD",
+  "CNY",
+  "HKD",
+  "SGD",
+  "INR",
+  "ZAR",
+  "BRL",
+  "MXN",
+  "SEK",
+  "NOK",
+  "DKK",
+  "PLN",
+  "TRY",
+  "KRW",
+  "RUB",
+  "THB",
+  "IDR",
+  "MYR",
+  "PHP",
+  "CZK",
+  "HUF",
+  "ILS",
+  "AED",
+  "SAR"
+]

addedInput schema / properties / to / description

Added value: +"Target ISO 4217 currency code (3 letters, case-insensitive). Same 31-code enum as from; equal from/to returns a rate of 1."

addedInput schema / properties / to / enum

Added value: +[
+  "USD",
+  "EUR",
+  "GBP",
+  "JPY",
+  "CHF",
+  "CAD",
+  "AUD",
+  "NZD",
+  "CNY",
+  "HKD",
+  "SGD",
+  "INR",
+  "ZAR",
+  "BRL",
+  "MXN",
+  "SEK",
+  "NOK",
+  "DKK",
+  "PLN",
+  "TRY",
+  "KRW",
+  "RUB",
+  "THB",
+  "IDR",
+  "MYR",
+  "PHP",
+  "CZK",
+  "HUF",
+  "ILS",
+  "AED",
+  "SAR"
+]

changedInput schema / required

Previous value: -[
-  "from",
-  "to",
-  "amount"
-]New value: +[
+  "from",
+  "to"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "properties": {
+        "amount": {
+          "description": "Input amount in the source currency as supplied.",
+          "type": "number"
+        },
+        "from": {
+          "description": "Normalised source ISO 4217 code.",
+          "type": "string"
+        },
+        "rate": {
+          "description": "Conversion rate: 1 unit of from equals this many units of to.",
+          "type": "number"
+        },
+        "rate_date": {
+          "description": "EOD date of the rate used, as YYYY-MM-DD.",
+          "format": "date",
+          "type": "string"
+        },
+        "rate_inverse": {
+          "description": "Inverse rate: 1 unit of to equals this many units of from.",
+          "type": "number"
+        },
+        "result": {
+          "description": "Converted amount in the target currency (amount times rate).",
+          "type": "number"
+        },
+        "to": {
+          "description": "Normalised target ISO 4217 code.",
+          "type": "string"
+        },
+        "via": {
+          "description": "How the rate was resolved.",
+          "enum": [
+            "direct",
+            "triangulation:USD",
+            "identity"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the conversion succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. Description adds valuable context: triggers on-demand fetch for stale pairs, not idempotent, results change daily, rate limited to 30 req/min. No contradictions.

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 front-loaded with main purpose and contains all necessary information without redundancy. Slightly long but each sentence adds value; could be trimmed slightly but remains effective.

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 complexity (caching, daily rates, rate limiting, 31 currencies) and presence of output schema, description fully covers what an agent needs to know: purpose, behavior, limitations, and alternatives.

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 coverage is 100% with detailed descriptions including enums, case-insensitivity, and equal from/to behavior. Description does not add new parameter information beyond what schema provides, so a baseline score of 3 is appropriate.

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?

Clearly states the tool converts a money amount between ISO 4217 currencies using daily EOD FX rates. Lists output fields and distinguishes from siblings by naming math_currency_converter_history and math_unit_converter.

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?

Explicitly tells when to use this tool (present-day conversion among the 31 supported currencies) and when to use alternatives (math_currency_converter_history for multi-day series, math_unit_converter for non-currency conversions). Also mentions rate limits.

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

Deploy Server