APIVerve

Worldwide Earthquakes

WorldwideEarthquakes

Read-only

Worldwide Earthquakes: Worldwide Earthquakes tracks global seismic activity recorded over the past hour. It delivers magnitudes, epicenter coordinates and depth, location names, tsunami warning flags, USGS event links and 24-hour activity summaries sourced from the USGS. Filter by minimum magnitude; paid plans list the past 24 hours, search around any point, and add 7- and 30-day counts, the month's largest quake and daily history. (Cost: 2 credits)

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

Input Schema

Name	Required	Description	Default
`lat`	No	Latitude to search around. With lon, returns only earthquakes within radius km, nearest first, each with distanceKm
`lon`	No	Longitude to search around (use with lat)
`daily`	No	Include one row per UTC day for the last 30 days: event count, largest magnitude and M4.5+ count
`period`	No	Time window: hour (the past hour) or day (the past 24 hours)	hour
`radius`	No	Search radius in kilometers around lat/lon
`minMagnitude`	No	Only return earthquakes of at least this magnitude

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds real context beyond that: the upstream source (USGS), the freshness window (past hour vs past 24 hours), and a cost of 2 credits per call, which an agent needs for budgeting. It does not discuss rate limits, but the output schema carries the return shape.

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?

The first sentence is well front-loaded with scope and return fields, but the leading 'Worldwide Earthquakes: Worldwide Earthquakes tracks...' restates the title verbatim, and the trailing sentence mixes a feature list, plan-tier caveats and a credit cost into one run-on. Half the text is padding relative to what an agent needs to call it.

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?

With an output schema present and strong annotations, the description only needs to cover source, scope and cost, which it does. The paid-plan feature mentions (7/30-day counts, month's largest quake) are not backed by any schema parameter and risk setting expectations the tool cannot fulfill, keeping it short of a 5.

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%, so the schema already explains lat/lon/radius, period, daily and minMagnitude in detail; the description only loosely restates filtering by minimum magnitude and searching around a point. It also advertises capabilities (7- and 30-day counts, the month's largest quake) that have no corresponding parameters, which adds noise rather than parameter meaning.

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 specific verb and resource ('tracks global seismic activity') and pins the scope to the past hour, then enumerates exactly what is returned (magnitude, epicenter coordinates, depth, location names, tsunami flags, USGS links). Combined with 'sourced from the USGS,' an agent can tell this is a live earthquake feed rather than a generic weather or geocoding sibling.

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 rather than stated: it says you can 'filter by minimum magnitude' and 'search around any point', which hints at how to call it, but there is no explicit when-to-use versus when-not, and no sibling (e.g. Weather, WeatherAlerts, MeteoriteLandings) is named as an alternative.

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

All APIVerve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.