Skip to main content
Glama

Search earthquakes near a location

search_earthquakes
Read-only

Search historical earthquakes near a WGS84 coordinate by radius, with optional date range and minimum magnitude filters to identify past seismic activity.

Instructions

Search historical seismic events near a WGS84 point within a radius, with optional date range (inclusive; date_to covers the whole day) and magnitude filter.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "search_earthquakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude of search centre
lonYesWGS84 longitude of search centre
limitNo
date_toNoEnd date YYYY-MM-DD (inclusive)
date_fromNoStart date YYYY-MM-DD (default: 1 year back)
radius_kmNo
min_magnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds genuinely useful semantics about date filtering (inclusive bounds, date_to covering the whole day), but says nothing about result ordering, total caps, or how "limit" truncates results – relevant for an open-world search.

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 dense sentence with the resource and spatial scope front-loaded, then the optional filters. It is efficient and free of filler, though the parenthetical about inclusive dates crowds the same sentence and slightly hurts scannability.

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?

Seven parameters with no output schema and only 57% schema description coverage leave real gaps: the description does not explain what an event record contains, what happens when limit is hit, or the default temporal window (which lives only in the schema). For a read-only search tool this is adequate but thin.

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 57%, so the description needs to add some meaning; it does clarify the inclusive date range and whole-day semantics of date_to. However, it leaves limit, min_magnitude (which has no schema description at all), and radius_km unelaborated, so the coverage gap is only partly compensated.

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 ("Search historical seismic events") plus the spatial scoping (near a WGS84 point within a radius), which is enough for an agent to distinguish it from unrelated siblings. The word "historical" implicitly separates it from get_recent_earthquakes, but neither that nor get_location_report is named explicitly.

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: "historical" versus the sibling get_recent_earthquakes suggests when this tool is appropriate, and the optional filters hint at refinement scenarios. There is no explicit when-to-use/when-not statement or named alternative, so an agent must infer the routing decision.

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