Skip to main content
Glama

get_exchange_rate_history

Read-onlyIdempotent

Retrieve historical SNB monthly-average CHF exchange rates for a specified currency, with optional from/to date range (default: last 90 months).

Instructions

Historical SNB monthly-average CHF exchange rates (default: last 90 months)

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": {
      "currency": "<currency>"
    },
    "name": "get_exchange_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM
fromNoYYYY-MM
currencyYesISO 4217 code, e.g. EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / currency / description
      Previous value: -"ISO 4217 currency code (e.g. 'EUR', 'USD', 'GBP'). Use list_currencies to see all available codes."New value: +"ISO 4217 code, e.g. EUR"
    • changedInput schema / properties / from / description
      Previous value: -"Start date in YYYY-MM format (e.g. '2020-01'). Optional."New value: +"YYYY-MM"
    • changedInput schema / properties / to / description
      Previous value: -"End date in YYYY-MM format (e.g. '2026-02'). Optional."New value: +"YYYY-MM"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add operational context, which it does: it discloses the data source (SNB), the granularity (monthly averages), and the default behavior when from/to are omitted (last 90 months). It stops short of describing output shape, pagination, or a maximum retrievable range.

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?

A single front-loaded fragment with zero filler, and the most decision-relevant qualifier ('Historical') leads. The trade-off is that its terseness borders on telegraphic, with the default-range note parenthesized rather than integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only three simple parameters and no output schema, the description is close to sufficient, but it leaves the return format unspecified — an agent cannot tell whether values are CHF-per-unit-of-currency or the inverse, nor whether the response is a keyed series or a list. For a data-retrieval tool whose whole value is the shape of the series, that is a real gap.

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 coverage is 100%, so the baseline is 3, but the description earns a bump by explaining the default window of 90 months that applies when the optional from/to bounds are absent, which the schema does not state. It also clarifies the quote currency is CHF, disambiguating the direction of the returned rates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (historical SNB monthly-average CHF exchange rates) and implicitly distinguishes itself from the sibling get_exchange_rate by the word 'Historical'. The verb is elided, and it never names get_exchange_rate directly, so differentiation is inferred rather than stated.

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?

Usage is only implied: 'Historical' suggests a time series rather than a spot rate, which points an agent away from get_exchange_rate. There is no explicit when-to-use statement, no mention of range limits, and no guidance on what to do if the requested window predates the data.

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

Deploy Server

Other Tools