Skip to main content
Glama

Avalanche danger at coordinates

get_avalanche_danger_at
Read-only

Get the avalanche danger level for a WGS84 point, such as a ski-touring destination, by resolving it against SLF warning-region polygons.

Instructions

Avalanche danger level for a specific WGS84 point (e.g. a ski-touring destination), resolved against the SLF warning-region polygons.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_avalanche_danger_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that by explaining the resolution mechanism (point mapped to SLF warning-region polygons), but omits the danger-level scale/units and what is returned when a point falls outside all polygons.

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?

A single front-loaded sentence with the resource first, the scope second, and the resolution mechanism last. Nothing is padding and no sentence could be removed without loss.

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 two-parameter read-only lookup with full schema coverage and no output schema, this is nearly complete; the resolution mechanism is a valuable addition. The remaining gaps — danger-scale units and out-of-coverage behavior — are minor for a point query.

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% and both parameters already carry WGS84 lat/lon descriptions with bounds. The description's reference to 'WGS84 point' and the example coordinate use add only light framing beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific resource (avalanche danger level) and a precise scope (a single WGS84 point), and distinguishes itself from bulletin-style lookups by noting the point is resolved against SLF warning-region polygons. It stops short of naming the sibling bulletin tool, but the verb+resource+scope are unambiguous.

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?

The parenthetical 'e.g. a ski-touring destination' implies the intended use case, giving an agent a reasonable contextual cue. There is no explicit when-not guidance, no stated alternatives, and no mention of behavior for coordinates outside the covered alpine extent.

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