Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

get_fx_rates

Read-onlyIdempotent

utilpeek: foreign-exchange reference rates for a base currency. For live on-chain rates use get_live_fx_rates. Unknown currencies and older dates are a 422 (not charged); an ECB outage is a 5xx (not charged). Typically under 0.1 s (up to 10 s on a refresh). Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Rates are the European Central Bank (ECB) euro reference rates, available free of charge at ecb.europa.eu; non-EUR bases are cross rates computed by Tanod. For information purposes only, not for transactions (attribution carries the ECB terms). Docs: https://tanod.dev/learn/exchange-rates-api.html

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>"
    },
    "name": "get_fx_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesBase currency (ISO 4217, e.g. USD), or EUR.
dateNoYYYY-MM-DD within the last 90 days (default: latest).
symbolsNo1-40 ISO 4217 codes to return (default: all ECB currencies).

Output Schema

NameRequiredDescriptionDefault
baseNo
dateNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
ratesNo
staleNo
cachedNo
attributionNo
requested_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / base / title
      Removed value: -"Base"
    • removedInput schema / properties / date / default
      Removed value: -null
    • changedInput schema / properties / date / description
      Previous value: -"Optional YYYY-MM-DD within the last 90 days (default: latest)."New value: +"YYYY-MM-DD within the last 90 days (default: latest)."
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • removedInput schema / properties / symbols / default
      Removed value: -null
    • changedInput schema / properties / symbols / description
      Previous value: -"Optional: 1-40 ISO 4217 codes to return (default: all ECB currencies)."New value: +"1-40 ISO 4217 codes to return (default: all ECB currencies)."
    • removedInput schema / properties / symbols / title
      Removed value: -"Symbols"
    • removedInput schema / title
      Removed value: -"get_fx_ratesArguments"
    • removedOutput schema / properties / attribution / properties
      Removed value: -{
      -  "disclaimer": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "free_of_charge": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "modification": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "source": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / rates / additionalProperties
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {
      +      "properties": {
      +        "disclaimer": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "free_of_charge": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "modification": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "source": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "url": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "base": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "cached": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "rates": {
      +      "additionalProperties": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "requested_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "stale": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, but the description adds materially more: which failures are billed and which are not, typical and worst-case latency (0.1 s, up to 10 s on refresh), price per call, free-tier quota per IP per UTC day, and the upstream data source. It also discloses provenance/licensing (ECB terms carried in `attribution`) and a not-for-transactions disclaimer, which is exactly the sort of context annotations cannot express.

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?

Front-loaded with purpose and the sibling disambiguation, then cost/error/latency facts in a compact sequence. A few clauses (full attribution paragraph, full docs URL, 'available free of charge at ecb.europa.eu') are heavier than the calling decision requires, but nothing is genuinely wasted.

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?

An output schema exists so return values need no explanation, and the parameters are fully documented in the schema. What remains — billing, error classes, latency, quota, provenance, and sibling routing — is all covered, so an agent has everything needed to call it correctly and to set user expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns one more by explaining that non-EUR bases are Turandot-computed cross rates rather than direct ECB quotes, which changes how `base` output should be interpreted. It does not add formatting or default syntax beyond the schema, so it falls short of a 5.

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?

States a specific resource and scope: 'foreign-exchange reference rates for a base currency.' It also names the sibling it is not — 'For live on-chain rates use get_live_fx_rates' — so an agent can route between the two without opening either schema.

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?

Gives an explicit alternative plus the condition that selects it (live on-chain rates -> get_live_fx_rates), and further defines the usage envelope via the 90-day/known-currency constraints and chargeability rules for 422 vs 5xx.

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.