Skip to main content
Glama

Current CHF exchange rate

get_exchange_rate
Read-only

Retrieve the official SNB exchange rate of a currency against CHF, expressed as CHF per N units, to convert or compare foreign-currency values using verified monthly averages.

Instructions

Latest official SNB exchange rate for a currency against CHF (monthly average, e.g. EUR, USD, GBP, JPY). Rates are 'CHF per N units of foreign 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 currency code, e.g. 'EUR', 'USD', 'GBP', 'JPY'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, openWorld), and the description adds real behavioral content beyond them: the figure is a monthly average rather than a live tick, and the quoting convention is 'CHF per N units of foreign currency'. The unit convention is the most important detail here since it determines how the returned number must be interpreted or inverted. It does not clarify what N is for currencies like JPY.

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?

Two tightly packed sentences with no filler; the resource and scope come first and the unit convention follows as the necessary interpretation note.

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?

For a one-parameter lookup with no output schema, the definition covers what it returns and in what units, which is the key ambiguity. The remaining gap is the unspecified 'N' multiplier per currency, which matters for interpreting JPY-style quotes.

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% for the single 'currency' parameter, including its ISO-code format and examples, so the baseline applies. The description's own '(e.g. EUR, USD, GBP, JPY)' largely repeats the schema and adds no new constraint or validation detail.

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 verb+resource: 'Latest official SNB exchange rate for a currency against CHF', and the word 'Latest' implicitly separates it from get_exchange_rate_history. It stops short of explicitly naming that sibling, so the 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 implied by 'Latest' plus the single-currency framing, which suggests a point lookup rather than a time series. There is no explicit when-to-use/when-not statement and no named alternative such as the history tool, so an agent must infer routing.

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