Skip to main content
Glama

List SNB-published currencies

list_currencies
Read-only

Returns all currencies for which the SNB publishes official CHF exchange rates, so you can look up supported Swiss National Bank rate codes before requesting quotes.

Instructions

List all currencies for which the SNB publishes official 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 observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely useful disclosure beyond them: the result is restricted to SNB-published CHF-rate currencies, not all ISO currencies, which prevents a wrong assumption. It says nothing about the return shape or ordering, but with annotations doing the heavy lifting that gap is minor.

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 clause (currencies, SNB-published, official CHF rates) carries information.

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 zero-parameter enumeration tool with annotations present and no output schema, the definition covers what the tool returns in scope terms. Only the concrete shape of the returned items (codes vs. names) is left implicit, which is a small residual gap.

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 parameter meaning to convey; the baseline for a no-param schema 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?

States a specific verb and resource (list currencies) plus a meaningful scope qualifier: only currencies for which the SNB publishes official CHF rates. That qualifier separates it from generic code-list lookups such as lookup_code_list, though the description does not name any sibling 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 scope statement implies when the tool applies (you need the set of currencies with official CHF rates), but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as lookup_code_list for resolving a single code.

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