Skip to main content
Glama

Get Active Weather & Hazard Warnings (CAP)

get_weather_warnings
Read-onlyIdempotent

Returns active Common Alerting Protocol (CAP) weather and natural-hazard warnings from Veðurstofa Íslands (api.vedur.is/cap), returning an explicit empty state when none are active (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_weather_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum active alerts to return (1-20, default 20).
regionNoOptional forecast area or keyword filter (e.g. Capital, South, Faxaflói, Westfjords, North, East).
categoryNoOptional CAP alert category filter (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds genuinely new behavior: the upstream endpoint, a hard result cap of 20, and an 'explicit empty state' when nothing is active — the last being useful for an agent deciding how to interpret a null-ish response.

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?

A single front-loaded sentence with no filler; the source URL and empty-state behavior are the only parenthetical extras and both carry information. Slightly dense, but nothing is wasted.

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?

With no output schema, the description should hint at the shape of returned alerts, but it only mentions the empty state and the 20-item cap — nothing about fields such as severity, area, or validity times. Adequate for calling the tool, thin for interpreting results.

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, region, category) are already fully documented with ranges, examples and enum values. The description's only parameter-relevant content is the '(max 20)' cap, which merely restates the schema's maximum.

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 names a specific verb and resource ('Returns active Common Alerting Protocol (CAP) weather and natural-hazard warnings') plus the authoritative source (Veðurstofa Íslands). That is clear enough to separate it from forecast/earthquake/road-condition siblings, though it never explicitly contrasts with them.

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?

Usage is only implied by the word 'active' – an agent can infer this is for current alert conditions rather than forecasts. There is no explicit when-to-use statement, no exclusion of related siblings like get_weather or get_volcano_status, and no note on how hazard categories overlap with those tools.

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