Skip to main content
Glama

get_avalanche_conditions

Read-onlyIdempotent

Get current avalanche danger conditions in Iceland from Vedur.is.

Returns danger level (1-5), trend, snow conditions, and travel advisory per region. Critical for winter travel safety in mountainous areas.

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_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoRegion name, e.g. 'Trollaskagi', 'Vestfirdir', 'Sudurland', or 'all' for all regions.all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety behavior is covered. The description usefully adds the upstream source (Vedur.is) and the per-region content (danger level 1-5, trend, snow conditions, travel advisory), but says nothing about update frequency, caching, or what happens when no forecast is published — relevant for a live external feed.

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?

Three short sentences, front-loaded with the core action and source, followed by return content and context. Little waste; the safety sentence is justification rather than filler, though it could be folded more tightly into the purpose line.

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 an output schema present, the description needn't enumerate return fields in detail, and annotations cover the safety profile. What remains thin is freshness/staleness behavior and the validity scope of the data (winter season), which an agent would want for a live external feed.

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 the single region parameter already documents its examples and 'all' default, so the description's only contribution is the phrase 'per region,' which confirms results are broken down regionally. That is a small addition over an already complete schema, matching the baseline 3.

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?

States a specific verb and resource ('Get current avalanche danger conditions in Iceland') plus the data source (Vedur.is), which is more than the name alone conveys. It does not explicitly distinguish itself from plausible neighbors like get_safety_alerts or get_weather, so it stops short of a clean 5.

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?

'Critical for winter travel safety in mountainous areas' implies a usage context but never states when to prefer this over get_safety_alerts or get_weather, nor any exclusion such as off-season periods when no forecast exists. Usage is inferred rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources