Skip to main content
Glama

search_earthquakes_by_location

Read-onlyIdempotent

Find earthquakes within a chosen radius of a WGS84 coordinate, filtered by past days, minimum magnitude, and result limit.

Instructions

Earthquakes within a radius of a WGS84 point (SED)

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lonYesLongitude (WGS84)
daysNoPast days, max 365
limitNomax 100
radius_kmNokm, max 500
min_magnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.9.0
    • addedInput schema / properties / days / default
      Added value: +90
    • changedInput schema / properties / days / description
      Previous value: -"Number of past days to search (default: 90, max: 365)"New value: +"Past days, max 365"
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude of the center point (decimal degrees, e.g. 46.9 for Bern)"New value: +"Latitude (WGS84)"
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return (default: 20, max: 100)"New value: +"max 100"
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude of the center point (decimal degrees, e.g. 7.5 for Bern)"New value: +"Longitude (WGS84)"
    • addedInput schema / properties / min_magnitude / default
      Added value: +0.5
    • removedInput schema / properties / min_magnitude / description
      Removed value: -"Minimum magnitude filter (default: 0.5)"
    • addedInput schema / properties / radius_km / default
      Added value: +50
    • changedInput schema / properties / radius_km / description
      Previous value: -"Search radius in kilometres (default: 50, max: 500)"New value: +"km, max 500"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds only that the query is radius-based over a WGS84 point from SED data; it says nothing about result ordering, cap behavior across the days/limit/radius limits, or that out-of-range values are bounded.

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 short line with no filler, and the spatial constraint is front-loaded. It is concise to the point of under-specification rather than padded, so it does not lose points for waste.

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?

With six parameters, no output schema and four annotations, the definition is minimally adequate: the schema documents five of six parameters with defaults and maximums. What is missing is behavioral context an agent would want before calling, such as whether results are sorted by time, distance or magnitude, and whether the search is Swiss-only.

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 83% with per-parameter descriptions and defaults for days, limit and radius_km, so the schema carries most of the semantics. The description repeats only the WGS84 framing and adds nothing on min_magnitude, which is the one parameter with no schema description, nor on how the filters combine.

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) and the defining scope (within a radius of a WGS84 point), which separates it from the sibling get_recent_earthquakes that has no spatial filter. The parenthetical 'SED' (Swiss Seismological Service) is opaque to an agent and there is no verb, so it falls short of fully self-explanatory.

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?

The description gives no when-to-use guidance and never mentions the obvious alternatives in the sibling list (get_recent_earthquakes for a general feed, get_earthquake_details for a single event). The agent must infer routing from the tool name alone.

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