Skip to main content
Glama

Get Recent Earthquakes in Iceland

get_recent_earthquakes
Read-onlyIdempotent

Returns recent seismic events from the Icelandic Meteorological Office (Veðurstofa Íslands, api.vedur.is/quakes), filtered by minimum magnitude, lookback hours (1-168), and optional region/seismic zone, newest first (max 20), plus explicit felt-earthquake API availability metadata.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoLookback window in hours (1-168, default 24).
limitNoMaximum earthquakes to return (1-20, default 20).
regionNoOptional region or seismic zone filter (e.g. Reykjanes, Svartsengi, Askja, Katla, Bárðarbunga, Tjörnes, South).
min_magnitudeNoMinimum moment magnitude (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 usefully adds the ordering ('newest first'), a hard result cap (max 20), and upstream provenance, but the trailing phrase about 'felt-earthquake API availability metadata' is opaque and does not explain what the caller actually receives.

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 that puts source, filters and ordering before details, with no filler. The final clause about 'felt-earthquake API availability metadata' is vague jargon that weakens an otherwise tight sentence.

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 read-only tool with no output schema, the description should say what each returned quake contains (magnitude, depth, location, time), and it does not. Ordering and the 20-item cap are covered, but the payload shape and the meaning of the 'felt-earthquake metadata' remain undefined.

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 coverage is 100% and every parameter already carries a description, ranges and defaults, so the baseline is 3. The description mostly restates those ranges (1-168 hours, magnitude filter, region/zone) without adding format or 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?

States a specific verb and resource ('Returns recent seismic events') plus the upstream source (Icelandic Meteorological Office / api.vedur.is/quakes) and scope (magnitude/hours/region filters). It is clearly a distinct data source from hazard or status siblings, though it never explicitly contrasts itself with get_volcano_status or get_eruption_hazards.

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 filter defaults and ranges imply typical use (recent quakes within a lookback window, optionally narrowed by zone), but there is no explicit when-to-use guidance or statement of when another tool is the better pick. An agent must infer that this is the seismic-event counterpart to the volcano/hazard siblings.

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