Skip to main content
Glama

exchange-rates-mcp-server

Fx Convert Currency

fx_convert_currency
Read-onlyIdempotent

Convert an amount between any two currencies at the latest or a historical rate. Returns the converted amount, the rate used, the actual rate date, and whether the date was snapped to the prior published date. Cross-rates are triangulated through EUR automatically.

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_currency": "<base_currency>",
      "quote_currency": "<quote_currency>",
      "amount": "<amount>"
    },
    "name": "fx_convert_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO 8601 date (YYYY-MM-DD) for a historical rate. Omit for the latest available rate. Frankfurter v1 data starts 1999-01-04. Future dates are not supported.
amountYesAmount in the base currency to convert. Must be greater than zero.
base_currencyYesISO 4217 source currency code (e.g. USD). Call fx_list_currencies to get valid codes.
quote_currencyYesISO 4217 target currency code (e.g. EUR). The amount will be expressed in this currency. Call fx_list_currencies to get valid codes.

Output Schema

NameRequiredDescriptionDefault
rateNoExchange rate used: units of quote currency per 1 unit of base currency.
errorNoPresent when the call failed. Absent on success.
sourceNoAlways "Frankfurter v1" — the upstream data provider.
rate_dateNoActual date of the rate used for conversion.
rate_typeNoAlways "Daily rate (Frankfurter v1)" — these are reference rates, not tradeable bid/ask.
base_amountNoThe input amount in the base currency.
date_snappedNoTrue when rate_date differs from the requested date: the requested date was a weekend or holiday, or its daily fix was not yet published. Frankfurter v1 snaps such requests to the prior published date. Always false when date is omitted.
quote_amountNoThe unrounded amount × rate product in the quote currency, using JavaScript floating-point precision; no currency minor-unit rounding policy is applied.
base_currencyNoSource currency code.
quote_currencyNoTarget currency code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / date_snapped / description
      Previous value: -"True when the API returned a different date than requested — Frankfurter v1 snaps weekend/holiday requests to the prior business day."New value: +"True when rate_date differs from the requested date: the requested date was a weekend or holiday, or its daily fix was not yet published. Frankfurter v1 snaps such requests to the prior published date. Always false when date is omitted."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_date_format`: date is not a real calendar date written as YYYY-MM-DD. `unsupported_currency`: base_currency or quote_currency is not available in the current discovery or served historical data. `date_out_of_range`: date is before 1999-01-04 or in the future. `upstream_no_data`: Both currencies are supported but the Frankfurter v1 published no rate for this date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_date_format`: date is not a real calendar date written as YYYY-MM-DD. `unsupported_currency`: base_currency or quote_currency is not available in the current discovery or served historical data. `date_out_of_range`: date is before 1999-01-04 or in the future. `upstream_no_data`: Both currencies are supported but Frankfurter v1 has no observation for a requested currency on this date. Other values are possible when a failure originates below the handler."
  2. Changed1 schema field changed
    • changedOutput schema / properties / quote_amount / description
      Previous value: -"The converted amount in the quote currency, rounded to 6 decimal places."New value: +"The unrounded amount × rate product in the quote currency, using JavaScript floating-point precision; no currency minor-unit rounding policy is applied."
  3. Changed6 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"ISO 8601 date (YYYY-MM-DD) for a historical rate. Omit for the latest available rate. ECB data starts 1999-01-04. Future dates are not supported."New value: +"ISO 8601 date (YYYY-MM-DD) for a historical rate. Omit for the latest available rate. Frankfurter v1 data starts 1999-01-04. Future dates are not supported."
    • addedInput schema / properties / date / pattern
      Added value: +"^(?:\\d{4}-\\d{2}-\\d{2}|latest)$"
    • changedOutput schema / properties / date_snapped / description
      Previous value: -"True when the API returned a different date than requested — ECB silently snaps weekend/holiday requests to the prior business day."New value: +"True when the API returned a different date than requested — Frankfurter v1 snaps weekend/holiday requests to the prior business day."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_date_format`: date is not a real calendar date written as YYYY-MM-DD. `unsupported_currency`: base_currency or quote_currency is not in the ECB currency set. `date_out_of_range`: date is before 1999-01-04 or in the future. `upstream_no_data`: Both currencies are supported but the ECB published no rate for this date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_date_format`: date is not a real calendar date written as YYYY-MM-DD. `unsupported_currency`: base_currency or quote_currency is not available in the current discovery or served historical data. `date_out_of_range`: date is before 1999-01-04 or in the future. `upstream_no_data`: Both currencies are supported but the Frankfurter v1 published no rate for this date. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / rate_type / description
      Previous value: -"Always \"ECB reference (mid-market)\" — these are reference rates, not tradeable bid/ask."New value: +"Always \"Daily rate (Frankfurter v1)\" — these are reference rates, not tradeable bid/ask."
    • changedOutput schema / properties / source / description
      Previous value: -"Always \"ECB via Frankfurter\" — the upstream data provider."New value: +"Always \"Frankfurter v1\" — the upstream data provider."
  4. Changed1 schema field changed
    • changedInput schema / properties / quote_currency / description
      Previous value: -"ISO 4217 target currency code (e.g. EUR). The amount will be expressed in this currency."New value: +"ISO 4217 target currency code (e.g. EUR). The amount will be expressed in this currency. Call fx_list_currencies to get valid codes."
  5. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "base_currency",
      +      "quote_currency",
      +      "base_amount",
      +      "quote_amount",
      +      "rate",
      +      "rate_date",
      +      "date_snapped",
      +      "rate_type",
      +      "source"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `invalid_date_format`: date is not a real calendar date written as YYYY-MM-DD. `unsupported_currency`: base_currency or quote_currency is not in the ECB currency set. `date_out_of_range`: date is before 1999-01-04 or in the future. `upstream_no_data`: Both currencies are supported but the ECB published no rate for this date. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "invalid_date_format",
      +            "unsupported_currency",
      +            "date_out_of_range",
      +            "upstream_no_data"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "base_currency",
      -  "quote_currency",
      -  "base_amount",
      -  "quote_amount",
      -  "rate",
      -  "rate_date",
      -  "date_snapped",
      -  "rate_type",
      -  "source"
      -]
  6. Changed2 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in the base currency to convert. Must be a positive number."New value: +"Amount in the base currency to convert. Must be greater than zero."
    • addedInput schema / properties / amount / exclusiveMinimum
      Added value: +0
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world, so the safety profile is covered. The description adds genuine behavioral context not in the annotations: that cross-rates are triangulated through EUR automatically and that a requested date may be snapped to the prior published date, which affects how the agent should interpret results.

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?

Two sentences, both front-loaded with the conversion capability before the return details, and no filler. The enumeration of return fields overlaps with the existing output schema, which is mildly redundant but still clarifies the snapped-date semantics.

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 an output schema, full annotation coverage, and 100% schema description coverage, the description only needs to add behavioral nuance, which it does via triangulation and date snapping. Error behavior for invalid currency codes is not covered, but the schema already directs the agent to fx_list_currencies for valid codes.

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%, so all four parameters, including the date pattern and the 1999-01-04 data floor, are already documented in the schema. The description only restates that either a latest or historical rate can be selected, adding no syntax or format detail beyond the structured fields.

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 names a specific verb and resource ('Convert an amount between any two currencies') and scopes it to latest or historical rates, which separates it from rate-lookup siblings like fx_get_rate. It also discloses the cross-rate triangulation behavior, so an agent knows it can request pairs that have no direct quote.

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?

It implies when to use historical vs latest ('at the latest or a historical rate', plus the schema note to omit the date for latest), but it never explicitly routes the agent away from fx_get_rate or fx_get_rates when only a rate is needed. Usage is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.