SnowSure

Overview Schema Source Related Servers Discussions Admin

Avalanche bulletin

get_avalanche

Read-onlyIdempotent

Access current avalanche danger bulletins for resort forecast zones, relayed from official warning services with issuer and link. Useful for pre-trip safety planning.

Instructions

Current avalanche danger bulletin for a resort's forecast zone (US, Canada, Switzerland in v1), relayed from the official warning service with the issuer + link. Returns 'no bulletin' when there's no forecast service for the area or it's off-season. NOT a substitute for the official bulletin or avalanche training.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Resort slug, e.g. jackson-hole

Output Schema

TableJSON Schema

Name	Required	Description	Default
`markdown`	No	Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds that the bulletin is relayed from official warning service with issuer and link, and specifies behavior when no bulletin exists. No contradictions with annotations.

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: first states purpose, second covers edge cases and warnings. No unnecessary words, front-loaded with key action and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description is complete for a read-only tool with output schema present. Covers geographic scope, behavior for missing data, source attribution, and important caveat about training. No missing context.

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 100% with 'slug' described adequately. Description does not add further parameter details beyond what schema provides, meeting the baseline for high 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?

Description clearly states verb 'get' and resource 'avalanche danger bulletin' with geographic scope (US, Canada, Switzerland). It distinguishes from sibling tools like get_snow_report or get_weather_forecast by focusing specifically on official avalanche bulletin.

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?

Provides context for when to expect 'no bulletin' (off-season, no forecast service) and includes a caveat about not being a substitute for official bulletin or training. However, it does not explicitly compare to sibling tools or state when NOT to use it versus alternatives.

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