Skip to main content
Glama

get_avalanche_bulletin

Read-onlyIdempotent

Fetch live SLF avalanche bulletin data, including danger level, avalanche problems and advice, for a Swiss region, a coordinate, or all of Switzerland, or for an archived date.

Instructions

Live SLF avalanche bulletin: danger level (1-5), avalanche problems with aspect and elevation, validity and advice text, for one warning region, a coordinate, or all of Switzerland. Outside the winter season it reports that no bulletin is in force

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": "get_avalanche_bulletin"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude, with lon; alternative to region
lonNoWGS84 longitude, with lat
dateNoYYYY-MM-DD or ISO timestamp for an archived bulletin; omit for the current one
regionNoEAWS region id (e.g. CH-7114) or name, see list_avalanche_regions
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.0
    • addedInput schema / properties / date
      Added value: +{
      +  "description": "YYYY-MM-DD or ISO timestamp for an archived bulletin; omit for the current one",
      +  "type": "string"
      +}
    • addedInput schema / properties / language / default
      Added value: +"en"
    • removedInput schema / properties / language / description
      Removed value: -"Language for bulletin links: de (German), en (English), fr (French), it (Italian). Default: en"
    • addedInput schema / properties / lat
      Added value: +{
      +  "description": "WGS84 latitude, with lon; alternative to region",
      +  "type": "number"
      +}
    • addedInput schema / properties / lon
      Added value: +{
      +  "description": "WGS84 longitude, with lat",
      +  "type": "number"
      +}
    • changedInput schema / properties / region / description
      Previous value: -"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."New value: +"EAWS region id (e.g. CH-7114) or name, see list_avalanche_regions"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses what the payload contains and, importantly, that outside the winter season it returns a 'no bulletin in force' state rather than failing or returning empty.

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 sentences, both earning their place: the first front-loads the payload and scopes, the second covers the seasonal edge case. 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?

With no output schema, the description carries the return-value burden and does so well by describing the bulletin's fields and the off-season response. The gap is that the archived-bulletin capability (date parameter) and multilingual output (language parameter) are never surfaced, which an agent would only discover in the schema.

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 coverage is 80% and the parameters are self-documented, so the baseline is 3. The description does clarify the region-vs-coordinate-vs-omitted scoping modes, but it never mentions the date parameter for archived bulletins or the language enum, so it only partially extends meaning beyond the schema.

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 names the exact resource (live SLF avalanche bulletin) and enumerates its payload: danger level 1-5, avalanche problems with aspect and elevation, validity and advice text. It also states the three query scopes, so an agent can distinguish it from get_snow_conditions or get_weather without opening the schema.

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?

It gives clear usage context by listing the three input modes (warning region, coordinate, or all of Switzerland) and covers the out-of-season case. It stops short of explicit when-not-to-use guidance and does not contrast itself with the nearby sibling get_snow_conditions, which also reports alpine conditions.

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