Skip to main content
Glama

get_exchange_rate

Read-onlyIdempotent

Retrieve the Swiss National Bank's monthly average CHF exchange rate for a specified ISO currency code, such as EUR.

Instructions

Latest SNB monthly-average CHF exchange rate for a currency

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

Input Schema

NameRequiredDescriptionDefault
currencyYesISO 4217 code, e.g. EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / currency / description
      Previous value: -"ISO 4217 currency code (e.g. 'EUR', 'USD', 'GBP', 'JPY'). Use list_currencies to see all available codes."New value: +"ISO 4217 code, e.g. EUR"
  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 declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond that: the data source is the SNB, the figure is a monthly average rather than a spot/real-time quote, and the quote currency is CHF.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; every element (source, cadence, base currency, target currency) earns its place.

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?

For a one-parameter lookup with no output schema, the description is close to sufficient, but it leaves the quotation direction ambiguous (CHF per unit of foreign currency vs the reverse) and says nothing about how stale the 'latest' monthly average can be. These are small but real gaps for an agent interpreting the returned number.

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% and the single parameter already carries 'ISO 4217 code, e.g. EUR'. The description adds no further detail about the currency argument, so the baseline 3 applies.

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?

The description names a specific verb-less but precise resource: the latest SNB monthly-average CHF exchange rate for a currency. That clearly separates it from get_exchange_rate_history (historical series) and list_currencies (enumeration), though neither sibling is named explicitly.

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?

The word 'Latest' implies when to use this over get_exchange_rate_history, but the guidance is only implied. There is no explicit 'use this when you need the current month's rate, use history for time series' statement or any prerequisite note.

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