Skip to main content
Glama

list_avalanche_regions

Read-onlyIdempotent

Find Swiss avalanche warning regions by canton or search term to obtain IDs and names for retrieving current avalanche bulletins.

Instructions

The 135 SLF/EAWS avalanche warning regions (id, name, canton) for get_avalanche_bulletin

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

Input Schema

NameRequiredDescriptionDefault
cantonNoCanton code, e.g. GR
searchNoMatch on region id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Filter regions by canton abbreviation (e.g. GR, VS, BE). Optional."New value: +"Canton code, e.g. GR"
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Match on region id or name",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/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 genuine context beyond that: the upstream source (SLF/EAWS), the total size of the dataset (135), and the shape of each record. It says nothing about whether all 135 are always returned or how filtering narrows the result set.

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 compact clause with zero filler; the dataset identity and its linkage to the consumer tool are front-loaded. Nothing could be removed without losing information that is actually present.

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?

The tool is simple, has only optional parameters, full schema coverage, and no output schema, so the description does not need to explain return formatting. However, for a list tool it omits whether results are complete or paginated and how the two optional filters interact, which are the main things an agent needs before calling it.

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 both parameters (canton, search) are documented in the schema, so the baseline of 3 applies. The description contributes no additional parameter meaning — it never mentions the filters or explains that they are optional, mutually combinable, or how 'search' matching behaves.

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?

Names the specific resource (135 SLF/EAWS avalanche warning regions), enumerates the returned fields (id, name, canton), and distinguishes itself from the sibling get_avalanche_bulletin by framing itself as that tool's lookup source. The list verb is only implied via the tool name, so it stops just short of a fully self-contained purpose statement.

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 trailing 'for get_avalanche_bulletin' implicitly tells the agent this is a prerequisite lookup to obtain region ids before requesting a bulletin. There is no explicit when-to-use sentence, no statement that filters can be omitted to get all 135, and no guidance on choosing between the canton filter and the search filter.

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