Skip to main content
Glama

get_exchange_rates

Read-onlyIdempotent

Get current ISK exchange rates from the Central Bank of Iceland.

Returns buy/sell rates for ISK against major currencies. Updated daily on business days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exchange_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoISO currency code, e.g. 'EUR', 'USD', 'GBP'. Omit for all rates.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the data source (Central Bank of Iceland), the returned shape (buy/sell rates against major currencies), and freshness ('updated daily on business days'), which tells the agent results may be stale on weekends/holidays.

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?

Three short lines, front-loaded with the core action and source, followed by return content and update cadence. Every sentence carries information and there is no filler.

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 simple single-parameter read tool with an output schema, the description covers source, return content, and refresh cadence, which is sufficient for correct invocation. The one remaining ambiguity is rate direction (ISK per unit vs. units per ISK), which matters for conversion but is minor given the output schema exists.

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 description coverage is 100%, and the schema already explains the ISO currency code and that omitting it returns all rates. The description only adds the phrase 'against major currencies', which loosely bounds the valid currency set, so it sits at the baseline for a fully documented single parameter.

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 and resource ('Get current ISK exchange rates') and even the authoritative source (Central Bank of Iceland), so the tool's function is unambiguous. It does not need to differentiate from a sibling because no other rate/currency tool exists in the catalog, but it also makes no explicit statement of that scope.

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: an agent can infer this is the tool for currency conversion or price display in ISK. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternative of omitting the currency parameter (that cue lives only in the schema).

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.

Resources