Skip to main content
Glama

List recent earthquakes from USGS by magnitude and place

earthquakes
Read-only

Recent earthquakes from USGS, newest first: magnitude, place, time, depth, coordinates, tsunami flag and alert level. Filter by minimum magnitude, days back (max 30) and a radius around a point. Public domain data. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "earthquakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoPoint latitude, with lon and radiusKm
lonNoPoint longitude
daysNo1 to 30 (default 7)
limitNo1 to 50 (default 10)
radiusKmNoRadius in km around the point
minMagnitudeNo0 to 10 (default 4.5)

Output Schema

NameRequiredDescriptionDefault
daysNo
countNo
eventsNo
sourceNo
checkedAtNo
minMagnitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 open-world reach are covered. The description adds genuinely non-obvious behavior: the newest-first ordering, public-domain licensing, and a paid x402 model at $0.002 per successful call across USDC on Base/Solana plus ten other networks, with failed calls uncharged. That payment and billing-on-success detail is information an agent cannot get from any structured field; only rate limits and result-window semantics remain undisclosed.

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?

Three sentences, front-loaded with the payload and filters, with the commercial terms last where they belong. The returned-field enumeration is somewhat redundant given an output schema exists and the pricing sentence is dense, but no sentence is filler.

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, open-world data feed with a full output schema and existing annotations, the description covers scope, ordering, filtering strategy, freshness, and cost model. The only material omission is rate-limit or quota behavior on a paid endpoint, which an agent spending money would want to know.

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 100%, with each parameter already carrying type and bounds (days 1–30 default 7, limit 1–50 default 10, minMagnitude 0–10 default 4.5). The description reinforces the coupling of lat/lon/radiusKm into a single radius filter and restates the 30-day ceiling, which is mild added meaning rather than new semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (USGS earthquake feed), states the ordering (newest first), enumerates the fields returned (magnitude, place, time, depth, coordinates, tsunami flag, alert level), and lists the available filter axes. There is no ambiguity about what an agent gets back, and no sibling in the catalog overlaps with seismic data.

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 through the filter axes (minimum magnitude, days back capped at 30, radius around a point), which hints at how to scope a query. However, there is no explicit statement of when to reach for this tool versus another data source, and no guidance on choosing between the time-window mode and the radius mode when both are available.

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