Skip to main content
Glama

get_avalanche_bulletin

Retrieve current Swiss avalanche danger bulletins with daily updates, providing danger levels, regional data, and interactive map links for safety planning.

Instructions

Get the current Swiss avalanche danger bulletin from SLF (WSL Institute for Snow and Avalanche Research). Returns current bulletin URLs, danger level descriptions, and links to the interactive map. The bulletin is published daily at ~08:00 and updated at ~17:00 Swiss time (October–May).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoOptional region ID (e.g. CH-9 for Central Graubünden) or region name. Use list_avalanche_regions to see all options. If omitted, returns national overview.
languageNoLanguage for bulletin links: de (German), en (English), fr (French), it (Italian). Default: en

Implementation Reference

  • The handler function responsible for executing the 'get_avalanche_bulletin' tool. It constructs bulletin URLs and optional region-specific links.
    async function handleGetAvalancheBulletin(args: Record<string, string>): Promise<string> {
      const lang = SUPPORTED_LANGUAGES.includes(args.language) ? args.language : "en";
      const today = todayISO();
    
      // Find matching region if specified
      let matchedRegion: typeof SWISS_AVALANCHE_REGIONS[0] | undefined;
      if (args.region) {
        const query = args.region.trim().toLowerCase();
        matchedRegion = SWISS_AVALANCHE_REGIONS.find(
          (r) =>
            r.id.toLowerCase() === query ||
            r.name.toLowerCase().includes(query) ||
            r.canton.toLowerCase().includes(query)
        );
      }
    
      const pdfUrl = bulletinPdfUrl(lang);
      const mapUrl = whiteRiskUrl(lang);
    
      const result: Record<string, unknown> = {
        date: today,
        source: "SLF – WSL Institute for Snow and Avalanche Research",
        bulletin_url: {
          interactive_map: mapUrl,
          pdf_full: pdfUrl,
          pdf_regions: {
            de: "https://aws.slf.ch/api/bulletin/document/full/de",
            en: "https://aws.slf.ch/api/bulletin/document/full/en",
            fr: "https://aws.slf.ch/api/bulletin/document/full/fr",
            it: "https://aws.slf.ch/api/bulletin/document/full/it",
          },
        },
        danger_scale: DANGER_LEVELS,
        schedule: {
          morning_bulletin: "~08:00 CET/CEST",
          afternoon_update: "~17:00 CET/CEST",
          season: "October to May (daily). Summer bulletins are occasional.",
        },
        note:
          "The SLF JSON API requires authentication (used by the White Risk app). " +
          "Current danger levels are available via the interactive map at whiterisk.ch " +
          "or as PDF bulletins at the URLs above. " +
          "For programmatic access, contact SLF at lawinfo@slf.ch.",
      };
    
      if (matchedRegion) {
        result.region = {
          id: matchedRegion.id,
          name: matchedRegion.name,
          canton: matchedRegion.canton,
          typical_elevation_m: matchedRegion.elevation_m,
          bulletin_link: `${mapUrl}#region=${matchedRegion.id}`,
        };
        result.tip = `Check ${matchedRegion.name} (${matchedRegion.id}) on the interactive map: ${mapUrl}`;
      } else if (args.region) {
        result.region_not_found = args.region;
        result.tip = `Use list_avalanche_regions to see valid region IDs. Or visit ${mapUrl} for the full map.`;
      }
    
      return JSON.stringify(result);
    }
  • The definition and input schema for the 'get_avalanche_bulletin' tool.
    {
      name: "get_avalanche_bulletin",
      description:
        "Get the current Swiss avalanche danger bulletin from SLF (WSL Institute for Snow and Avalanche Research). " +
        "Returns current bulletin URLs, danger level descriptions, and links to the interactive map. " +
        "The bulletin is published daily at ~08:00 and updated at ~17:00 Swiss time (October–May).",
      inputSchema: {
        type: "object",
        properties: {
          region: {
            type: "string",
            description:
              "Optional region ID (e.g. CH-9 for Central Graubünden) or region name. " +
              "Use list_avalanche_regions to see all options. If omitted, returns national overview.",
          },
          language: {
            type: "string",
            enum: ["de", "en", "fr", "it"],
            description: "Language for bulletin links: de (German), en (English), fr (French), it (Italian). Default: en",
          },
        },
      },
    },
  • The registration within the main dispatcher where the 'get_avalanche_bulletin' tool is linked to its handler function.
    case "get_avalanche_bulletin":
      return handleGetAvalancheBulletin(args);
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: publication schedule (~08:00 and ~17:00 Swiss time), seasonal availability (October–May), and data source (SLF/WSL). It doesn't mention rate limits or authentication needs, but covers essential operational context.

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?

Two tightly focused sentences with zero waste. First sentence states purpose and outputs, second provides critical timing context. Every word earns its place, and information is front-loaded appropriately.

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 read-only tool with no output schema, the description provides excellent context about what's returned (URLs, descriptions, map links) and operational constraints. The main gap is lack of output format details, but given the tool's relative simplicity and clear purpose, this is minor.

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 already fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage through structured data alone.

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 specific action ('Get'), resource ('current Swiss avalanche danger bulletin from SLF'), and output ('Returns current bulletin URLs, danger level descriptions, and links to the interactive map'). It distinguishes from siblings like 'get_snow_conditions' or 'get_snow_measurements' by focusing on official danger bulletins rather than raw data.

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

Usage Guidelines4/5

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

The description provides clear context about when to use it (daily bulletins at specific times, October–May season) and references a sibling tool ('list_avalanche_regions') for parameter options. However, it doesn't explicitly state when NOT to use it or name alternatives for similar data.

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