Skip to main content
Glama

Recent earthquakes

get_recent_earthquakes
Read-only

Retrieve recent seismic events recorded by the Swiss Seismological Service, newest first, with optional magnitude and time-window filters for earthquake monitoring.

Instructions

The most recent seismic events recorded by the Swiss Seismological Service, newest first. Optionally filter by minimum magnitude. event_type is included only when the service reports it (it may include quarry blasts).

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
limitNo
days_backNoSearch window in days
min_magnitudeNoOnly events at or above this magnitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond that: result ordering, the data source, and the caveat that event_type is only sometimes reported and may include quarry blasts, which affects how an agent should interpret results. It stops short of describing volume, pagination, or geographic scope.

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?

Two short, front-loaded sentences with zero filler; the source and ordering come first. The magnitude-filter sentence partly repeats schema information, and the event_type remark is useful but sits in the same breath as the filtering note.

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 read-only, three-optional-parameter tool with no output schema, the description covers source, ordering, and a data-quality caveat. Remaining gaps such as the limit default, maximum result count, and geographic coverage are modest and largely recoverable from the 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 coverage is 67%, with days_back and min_magnitude already documented inline and only limit left bare. The description restates the magnitude filter but adds no syntax, defaults, or guidance on limit, so it neither compensates for the gap nor adds much 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 names a specific resource (seismic events from the Swiss Seismological Service) and its ordering ('newest first'), which lets an agent distinguish it from a general search. It does not name the sibling search_earthquakes or get_earthquake_details, so the differentiation is implicit rather than explicit.

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 'most recent' and 'optionally filter by minimum magnitude', which tells the agent this is the lightweight recent-events view. There is no explicit when-to-use vs when-not, and no alternative tool is named for broader historical or full-text searches.

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

Deploy Server

Other Tools