Skip to main content
Glama

Current avalanche bulletin

get_avalanche_bulletin
Read-only

Fetch the official Swiss SLF avalanche bulletin to check current danger ratings by warning region, elevation, and time; returns a clear no-bulletin result outside winter.

Instructions

The current official SLF avalanche bulletin for Switzerland: danger ratings (EAWS scale 1 low – 5 very high) per bulletin, each listing the warning regions it covers, with elevation/time breakdown where published. Outside winter the bulletin is empty and this tool reports that clearly.

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
limitNoMax bulletins (danger areas) to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real context beyond that: the source is the official SLF bulletin, results are per-bulletin with covered warning regions, and the seasonal empty state is reported explicitly rather than silently. It does not cover freshness/update cadence or rate behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and its contents, with the seasonal caveat placed last where it belongs. Slightly dense compound phrasing, but no filler sentences.

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 it well — enumerating ratings scale, warning regions, and elevation/time breakdown plus the empty-winter behaviour. Only minor gaps remain: ordering of bulletins and what limit counts against beyond 'danger areas'.

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?

The single limit parameter is fully documented in the schema (max 50, min 1, default 30), so the baseline is 3. The description's clarification that bulletin entries correspond to danger areas adds marginal meaning but no new syntax or ordering guidance.

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?

States a specific verb and resource — the current official SLF avalanche bulletin for Switzerland — and enumerates the returned content (EAWS 1–5 danger ratings, warning regions, elevation/time breakdown). An agent can immediately distinguish this from a point-location danger lookup such as get_avalanche_danger_at.

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?

Implies usage (national bulletin rather than a spot check) and warns that the bulletin is empty outside winter, which prevents misinterpretation of a null result. However, it never explicitly states when to prefer this tool over the sibling get_avalanche_danger_at, leaving that routing to inference.

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