Skip to main content
Glama

Get Weather Observations & Forecast for Iceland

get_weather
Read-onlyIdempotent

Returns latest live weather station observations from Veðurstofa Íslands (api.vedur.is/weather 10-min AWS & SYNOP) and optional short-term XML forecast (xmlweather.vedur.is) for a town or station in Iceland.

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": {
      "place": "<place>"
    },
    "name": "get_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesIcelandic town, landmark, or station name (e.g. Reykjavík, Keflavík, Grindavík, Vík, Selfoss, Höfn, Akureyri, Egilsstaðir, Ísafjörður).
include_forecastNoInclude short-term XML forecast entries when available (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, open-world operation with no destructive effects. The description adds useful context beyond that: the data is live, sourced from Icelandic weather APIs, based on 10-minute AWS and SYNOP observations, and the forecast is optional and availability-dependent.

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?

The definition is a single front-loaded sentence with no redundant framing. It is dense with useful source and freshness details, though source URLs and terms like 'AWS & SYNOP' add some jargon.

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 simple two-parameter read-only tool with no output schema, the description covers the data sources, location scope, and optional forecast behavior adequately. It does not describe the returned observation or forecast fields, but the essential information needed to call the tool correctly is present.

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 descriptions are fully covered at 100%, so the parameter meanings are already documented. The description reinforces that the location can be a town or station and that the forecast is optional, but it does not add format, matching behavior, or fallback semantics beyond the schema.

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 and action: it returns live weather station observations plus an optional short-term forecast for an Icelandic place. It clearly distinguishes weather observations/forecast from sibling warning, earthquake, road, and volcano tools by subject matter, though it does not explicitly name alternatives.

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 implied by the wording: use this for current weather observations or a short forecast in Iceland. There is no explicit when-to-use or when-not-to-use guidance, and it does not route agents to related tools such as get_weather_warnings when warnings are needed.

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