Skip to main content
Glama

list_currencies

Read-onlyIdempotent

Retrieves available currencies and their Swiss National Bank CHF exchange rates, so you can identify supported currency codes and compare CHF values.

Instructions

List currencies with SNB CHF exchange rates

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the rates are SNB-sourced CHF rates, implying official reference data rather than live trading quotes. It says nothing about whether rates are current-snapshot or how often they refresh, which matters given a history sibling exists.

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 short clause with the resource and the key data attribute front-loaded, and no filler. Nothing in it could be removed without losing information.

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 zero-parameter list tool with no output schema, the description covers the essentials — what is listed and that CHF rates are attached. It leaves gaps an agent would care about: whether the rates are a current snapshot, what the currency identifiers look like, and how the result relates to the dedicated exchange-rate tools.

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?

The tool takes zero parameters, so there is no schema semantics for the description to compensate for; the baseline for a parameterless tool applies. The description correctly implies an unfiltered full listing, which is consistent with an empty input schema.

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 has a clear verb and resource ('List currencies') plus a qualifier that the listing includes SNB CHF exchange rates, which tells an agent what data comes back. It does not, however, distinguish this from sibling tools like get_exchange_rate or get_exchange_rate_history, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus get_exchange_rate (single rate lookup) or get_exchange_rate_history. The description gives no context, prerequisites, or exclusions — the agent has to guess that this is the discovery/enumeration step before a rate lookup.

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