Skip to main content
Glama

CHF exchange rate history

get_exchange_rate_history
Read-only

Retrieve monthly average CHF exchange rates for a chosen currency over a specified YYYY-MM range to analyze historical trends and compare periods.

Instructions

Monthly average CHF exchange-rate history for a currency over a month range (YYYY-MM).

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

Input Schema

NameRequiredDescriptionDefault
currencyYesISO currency code, e.g. 'EUR'
to_monthNoEnd month YYYY-MM (default: current)
from_monthYesStart month YYYY-MM (range at most 240 months)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond them by disclosing that values are monthly averages (not daily quotes) anchored on CHF, which matters for interpretation, but it says nothing about gaps, missing months, or data freshness.

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 sentence that front-loads the resource, granularity and scope with zero filler. Nothing is redundant and nothing needs reordering.

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 simple three-parameter read tool this is adequate, but with no output schema the description should say what the response looks like — e.g. a series of month/rate pairs — and whether the rate is CHF-per-unit or the inverse. That omission leaves a real interpretive gap for an agent consuming the numbers.

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 schema already documents the YYYY-MM pattern, the 'default: current' behaviour for to_month and the 240-month cap on from_month. The description only restates the month-range concept, adding no format or constraint detail beyond the schema, 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 gives a specific resource (CHF exchange-rate history), a specific granularity (monthly averages) and a scoping parameter (month range in YYYY-MM). An agent can distinguish it from a spot-rate tool like get_exchange_rate by the word 'history' and 'monthly average', though the sibling is never 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?

Usage is implied rather than stated: an agent can infer this is the tool for historical/trend queries versus a current-rate lookup, but there is no explicit 'use this when...' statement, no exclusion, and no mention of behaviour for future or non-existent months.

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