Skip to main content
Glama

list_cantons

Read-onlyIdempotent

List all Swiss cantons and their codes to map canton names to identifiers for Swiss open data, geodata, or weather tasks.

Instructions

List cantons with codes

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 observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the marginal fact that codes are included in the result; it says nothing about size of the list, caching, or the fields per canton. With annotations doing most of the work, this is a modest but not empty contribution.

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?

Five words, front-loaded with the verb and resource. There is no filler, hedging, or redundant restatement of the title.

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 is adequate but leaves real gaps: it does not say what fields each canton carries (name, official code, abbreviation), nor that the returned codes are the keys expected by other canton-scoped sibling tools. Without an output schema, that return-shape information has nowhere else to live.

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 semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents the parameter surface.

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 cantons') and adds the payload detail ('with codes'). It is distinguishable from neighbors like list_postcodes_in_canton or get_traffic_by_canton, though it does not explicitly say so; a reader must infer that this is the unfiltered reference list of Swiss cantons.

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?

No when-to-use guidance at all. It does not say this is a reference/enumeration call to be used before calling list_postcodes_in_canton, get_traffic_by_canton, or get_dams_by_canton, nor that it takes no filters and should not be used to look up a specific canton's data.

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