Skip to main content
Glama

Get Icelandic Volcano Status (VONA & VALS)

get_volcano_status
Read-onlyIdempotent

Returns current aviation color codes (VONA) and volcanic alert levels (VALS) for Icelandic volcanic systems from Veðurstofa Íslands (api.vedur.is/volcanoes), sorted with elevated unrest first (max 20).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum volcano entries to return (1-20, default 20).
volcanoNoOptional volcano name or 3-letter code filter (e.g. REY, Reykjanes, Askja, Katla, Hekla, Grímsvötn).
active_onlyNoOnly return systems with elevated VONA aviation color or VALS level > 0 (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results are ordered with elevated unrest first, and the response is capped at 20 entries. It does not disclose refresh frequency or what happens when the volcano filter matches nothing, which matters for a live hazard feed.

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 sentence that front-loads the returned data types, then the source, then the ordering and size constraint. Every clause carries information and there is no boilerplate.

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

Completeness3/5

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

For a simple, annotation-covered read tool this covers the essentials, but there is no output schema, so the description is the only place an agent could learn the shape of a returned entry (color code, VALS level, volcano name, timestamps). It names the two headline fields but not the record structure or freshness, leaving a real gap for a tool with no return 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 description coverage is 100%, so all three parameters (limit, volcano, active_only) are already documented with ranges, defaults, and examples. The description only echoes the max-20 cap and the sort order; it adds no meaning about filter matching behavior (e.g. case sensitivity, partial name matching) beyond what the schema states. Baseline 3 is appropriate.

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 ('Returns'), a specific resource (aviation color codes VONA and alert levels VALS for Icelandic volcanic systems), and the upstream data source (Veðurstofa Íslands / api.vedur.is/volcanoes). The subject matter alone separates it cleanly from the earthquake, road, weather, and warning siblings.

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 domain makes the intended use implied (checking volcano/aviation alert status), but there is no explicit when-to-use statement, no mention of update cadence or whether these are live vs. cached values, and no guidance on when to prefer a weather or warning sibling instead. Adequate but leaves routing to inference.

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