Skip to main content
Glama

List Swiss cantons

list_cantons
Read-only

Fetch all 26 Swiss cantons and their two-letter abbreviations to use as filters for querying public data via Swissyphus tools.

Instructions

All 26 Swiss cantons with their two-letter abbreviations (used as filters across Swissyphus tools).

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_cantons"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely useful context beyond it: the result is a complete, fixed set of 26 entries and the abbreviations are the canonical filter values used elsewhere in the server. Minor tension: openWorldHint=true suggests open-ended external data, while 'all 26' asserts a closed enumeration, but this is a labeling detail rather than a contradicted claim.

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 return contents and then the practical use of the abbreviations. No filler, no restatement of the tool name.

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 no-parameter, no-output-schema lookup, the description says what will come back (cantons with abbreviations) and why it matters. It stops short of describing the exact return shape (array of objects vs. code-to-name map), which is the only remaining gap for an agent consuming the result.

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 nothing to disambiguate; the 4 baseline applies. The description correctly implies the call is unconditional and unfiltered.

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 states exactly what the tool returns: all 26 Swiss cantons plus their two-letter abbreviations. The resource is unambiguous and clearly distinct from the other list_* siblings (glaciers, currencies, waste types, etc.), though it conveys the action implicitly rather than naming a verb.

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?

There is no explicit 'use this when' statement, but the parenthetical 'used as filters across Swissyphus tools' implies the purpose: resolve canton codes before calling filter-bearing tools. Guidance is implied rather than stated, and no alternatives or exclusions are named.

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