Skip to main content
Glama

get_recent_earthquakes

Read-onlyIdempotent

Retrieve recent earthquake records for Switzerland and nearby areas, filtered by time range, magnitude, result limit, and optional quarry blasts.

Instructions

Recent earthquakes in and around Switzerland (SED, ETH Zürich)

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
daysNoPast days, max 365
limitNomax 100
min_magnitudeNo
include_blastsNoInclude quarry blasts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.0
    • addedInput schema / properties / days / default
      Added value: +30
    • changedInput schema / properties / days / description
      Previous value: -"Number of past days to search (default: 30, max: 365)"New value: +"Past days, max 365"
    • addedInput schema / properties / include_blasts / default
      Added value: +false
    • changedInput schema / properties / include_blasts / description
      Previous value: -"Include quarry blasts in results (default: false — earthquakes only)"New value: +"Include quarry blasts"
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return (default: 20)"New value: +"max 100"
    • addedInput schema / properties / min_magnitude / default
      Added value: +0.5
    • removedInput schema / properties / min_magnitude / description
      Removed value: -"Minimum magnitude filter (default: 0.5)"
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description contributes provenance (SED, ETH Zürich), which is useful for trust, but says nothing about how fresh 'recent' is, what the result cap is, or that blasts are excluded by default — all of which affect interpretation of the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded fragment with zero waste, but it is terse to the point of under-specification; the parenthetical source citation occupies a quarter of the text while the substantive behavior goes unstated.

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

Completeness2/5

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

For a 4-parameter, no-output-schema, time-sensitive data tool, an agent needs to know what 'recent' means, the update cadence, and how magnitude filtering affects results. None of that is present, so the definition is not complete enough to call confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, with days, limit and include_blasts documented in the schema but min_magnitude undocumented anywhere. The description adds no parameter meaning at all — notably it never explains that min_magnitude is a magnitude filter or that include_blasts adds quarry/quarry-blast events rather than tectonic ones.

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?

Names the resource (earthquakes) with a recency scope and a geographic scope (in and around Switzerland), plus the data source (SED, ETH Zürich). It is identifiable at a glance, though it doesn't distinguish itself from get_earthquake_details or search_earthquakes_by_location, which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus search_earthquakes_by_location or get_earthquake_details, and no guidance that this is the default/latest-results tool. The agent must infer the routing decision entirely from the tool name.

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