Skip to main content
Glama

exchange-rates-mcp-server

Fx List Currencies

fx_list_currencies
Read-onlyIdempotent

List current Frankfurter v1 currency codes and names with as_of, the latest served rate date. include_retired=true adds historical codes absent from the current set, each marked retired=true. Optional official ECB start_date/end_date are outer coverage bounds, not uninterrupted availability; read retired, not end_date, for retirement. Metadata outages are disclosed without failing current discovery. Historical availability remains validated from requested v1 data. Use this to disambiguate dollars (USD vs AUD vs CAD).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fx_list_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_retiredNoInclude historical codes absent from current v1 discovery, marked retired=true; default false. Optional official ECB coverage dates are outer bounds and may contain gaps.

Output Schema

NameRequiredDescriptionDefault
as_ofNoLatest served daily rate date for this current-discovery list; historical availability is checked against historical data.
countNoTotal number of supported currencies.
errorNoPresent when the call failed. Absent on success.
noticeNoDiscloses unavailable optional coverage metadata or incomplete coverage dates.
sourceNoAlways "Frankfurter v1" — the upstream data provider.
currenciesNoAll supported currencies, sorted alphabetically by code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / include_retired / description
      Previous value: -"Include historical codes absent from current v1 discovery, default false. Optional official ECB coverage dates are outer bounds and may contain gaps."New value: +"Include historical codes absent from current v1 discovery, marked retired=true; default false. Optional official ECB coverage dates are outer bounds and may contain gaps."
    • changedOutput schema / properties / currencies / items / properties / end_date / description
      Previous value: -"Last covered date in optional official ECB metadata; a date here does not imply retirement."New value: +"Last covered date in optional official ECB metadata; retired marks retirement, not this date."
    • addedOutput schema / properties / currencies / items / properties / retired
      Added value: +{
      +  "description": "True only for a historical code include_retired added because it is absent from current v1 discovery; false for every current code.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / currencies / items / required
      Previous value: -[
      -  "code",
      -  "name"
      -]New value: +[
      +  "code",
      +  "name",
      +  "retired"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / include_retired
      Added value: +{
      +  "description": "Include historical codes absent from current v1 discovery, default false. Optional official ECB coverage dates are outer bounds and may contain gaps.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / currencies / items / properties / end_date
      Added value: +{
      +  "description": "Last covered date in optional official ECB metadata; a date here does not imply retirement.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / currencies / items / properties / start_date
      Added value: +{
      +  "description": "First covered date in optional official ECB metadata; outer bound, not uninterrupted availability.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Discloses unavailable optional coverage metadata or incomplete coverage dates.",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "currencies",
      -      "count",
      -      "source"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "currencies",
      +      "count",
      +      "as_of",
      +      "source"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / as_of
      Added value: +{
      +  "description": "Latest served daily rate date for this current-discovery list; historical availability is checked against historical data.",
      +  "type": "string"
      +}
    • 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. 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": [
      +      "currencies",
      +      "count",
      +      "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.",
      +          "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: -[
      -  "currencies",
      -  "count",
      -  "source"
      -]
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuinely new behavior: retired codes are flagged rather than merely included, end_date is an outer bound rather than availability, retirement must be read from the retired flag, and metadata outages degrade without failing discovery. However, it introduces 'start_date/end_date' that do not appear as parameters, which risks an agent trying to pass them, and the sentence 'Historical availability remains validated from requested v1 data' is opaque rather than informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and output fields are front-loaded, which is good, but the middle is dense jargon and partially redundant — the include_retired behavior is stated in the description and again in the schema, and 'Historical availability remains validated from requested v1 data' conveys little. Several clauses earn their place (retired flag vs end_date), but the paragraph could be tightened without losing meaning.

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 present, the description need not enumerate return values, and it sensibly focuses on the tricky semantics of the retired flag and coverage bounds. For a one-optional-param read-only tool this is nearly complete; the only real gap is the unclear status of the referenced start_date/end_date, which the agent cannot map to any input field.

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% and the single optional parameter include_retired is fully documented in the schema, including the default and the retired=true marking. The description restates the same contract almost verbatim ('include_retired=true adds historical codes ... marked retired=true') without adding syntax, format, or cost information beyond it, so the baseline of 3 applies.

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?

'List ... Frankfurter v1 currency codes and names' is a specific verb plus resource, and the mention of 'as_of, the latest served rate date' tells the agent what the enumeration carries. This is clearly a reference/enumeration tool, distinguishable from the rate, conversion, timeseries, and dataframe siblings without opening any 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?

It gives a concrete motivating scenario: 'Use this to disambiguate dollars (USD vs AUD vs CAD)', which is a real reason to enumerate codes before calling a rate or conversion tool. It stops short of explicit when-not guidance or naming the sibling to use instead when the agent actually wants rates, so it is strong context without full routing.

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.