Skip to main content
Glama

list_avalanche_regions

Retrieve Swiss avalanche warning regions with IDs, names, cantons, and elevations for use with avalanche bulletins. Filter by canton if needed.

Instructions

List all Swiss avalanche warning regions as defined by SLF/EAWS. Returns region IDs, names, cantons, and typical elevations. Use region IDs with get_avalanche_bulletin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cantonNoFilter regions by canton abbreviation (e.g. GR, VS, BE). Optional.

Implementation Reference

  • The handler function 'handleListAvalancheRegions' that retrieves and formats the list of avalanche regions.
    async function handleListAvalancheRegions(args: Record<string, string>): Promise<string> {
      let regions = SWISS_AVALANCHE_REGIONS;
    
      if (args.canton) {
        const cantonQuery = args.canton.trim().toUpperCase();
        regions = SWISS_AVALANCHE_REGIONS.filter((r) =>
          r.canton.toUpperCase().includes(cantonQuery)
        );
      }
    
      const result = {
        count: regions.length,
        source: "SLF/EAWS Swiss Avalanche Warning Regions",
        regions: regions.map((r) => ({
          id: r.id,
          name: r.name,
          canton: r.canton,
          typical_elevation_m: r.elevation_m,
        })),
        usage: "Pass region ID (e.g. 'CH-9') to get_avalanche_bulletin for region-specific bulletin link",
        bulletin_map: "https://whiterisk.ch/en/conditions",
      };
    
      return JSON.stringify(result);
    }
  • The tool definition and schema for 'list_avalanche_regions'.
    {
      name: "list_avalanche_regions",
      description:
        "List all Swiss avalanche warning regions as defined by SLF/EAWS. " +
        "Returns region IDs, names, cantons, and typical elevations. " +
        "Use region IDs with get_avalanche_bulletin.",
      inputSchema: {
        type: "object",
        properties: {
          canton: {
            type: "string",
            description: "Filter regions by canton abbreviation (e.g. GR, VS, BE). Optional.",
          },
        },
      },
    },
  • The registration of 'list_avalanche_regions' in the avalanche tool dispatcher.
    case "list_avalanche_regions":
      return handleListAvalancheRegions(args);
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a list of regions with specific fields, which is basic behavioral info. However, it lacks details on permissions, rate limits, pagination, or error handling, leaving gaps for a read operation.

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?

The description is two sentences with zero waste: the first states purpose and returns, the second provides usage guidance. It is front-loaded with essential information and efficiently structured for clarity.

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 simple read tool with no annotations, no output schema, and one optional parameter, the description is mostly complete. It covers purpose, returns, and usage context. However, it lacks output format details (e.g., structure, pagination) and error scenarios, which could be helpful for an agent.

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%, so the schema fully documents the optional 'canton' parameter. The description adds no additional parameter semantics beyond what the schema provides, such as examples of canton abbreviations or filtering effects. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all Swiss avalanche warning regions'), specifies the data source ('SLF/EAWS'), and enumerates the returned fields ('region IDs, names, cantons, and typical elevations'). It distinguishes from siblings by focusing on avalanche regions, unlike other tools for weather, traffic, or data retrieval.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool ('Use region IDs with get_avalanche_bulletin'), providing a direct alternative and integration guidance. This helps the agent understand the tool's role in a workflow, though it doesn't specify when not to use it or compare with non-sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server