USGS Earthquakes

get_recent_earthquakes

Get recent earthquakes worldwide above a minimum magnitude.

Returns earthquake events from the USGS catalog sorted by time (newest first).
Useful for monitoring seismic activity globally.

Args:
    min_magnitude: Minimum magnitude to include (default 2.5). Use 4.5+ for significant quakes only.
    days: Number of days to look back (default 7, max 30).
    limit: Maximum number of earthquakes to return (default 50, max 500).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`limit`	No
`min_magnitude`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that results come from the USGS catalog and are sorted by time (newest first), which is useful behavioral context. However, it does not cover potential behaviors like delay in catalog updates, error handling, or whether results are limited by USGS API specifics. This is adequate but not rich.

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

Conciseness5/5

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

The description is front-loaded with the primary purpose, followed by a clear statement of the data source and ordering, then a brief use case, and finally structured parameter details. Every sentence contributes value, and the length is appropriate for the tool's complexity.

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?

The tool is simple with 3 optional parameters and an output schema exists, so return values don't need explanation. The description covers purpose, behavior, parameter semantics, and a use case. It does not discuss relationship to sibling tools or potential edge cases, but for a straightforward read-only API, this is nearly complete. Missing explicit sibling differentiation slightly reduces completeness.

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

Parameters5/5

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

The schema has 0% description coverage, but the Args section fully explains all three parameters: min_magnitude (with default and guidance for 'significant quakes'), days (with default and max), and limit (with default and max). This adds meaning beyond the schema's types and defaults, fully compensating for the lack of inline schema descriptions.

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 opens with a specific verb+resource combination: 'Get recent earthquakes worldwide above a minimum magnitude.' It clearly distinguishes this from siblings by emphasizing 'worldwide' and 'recent', and names the USGS catalog as the data source. This is a precise and unambiguous purpose.

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

Usage Guidelines4/5

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

It states a clear use case: 'Useful for monitoring seismic activity globally.' This provides context, but it does not explicitly mention when to use sibling tools like get_earthquake_detail or get_earthquakes_near, nor does it exclude alternatives. The absence of exclusions keeps it at 4 rather than 5.

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

All USGS Earthquakes tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_earthquake_detail retrieves specific event details by ID, get_earthquakes_near searches by geographic location with radius parameters, and get_recent_earthquakes fetches global recent events sorted by time. There is no overlap or ambiguity between these three functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (detail, earthquakes_near, recent_earthquakes). The naming is uniform, predictable, and clearly indicates the action and target resource.

Tool Count4/5

Three tools are reasonable for a focused earthquake data server, covering key use cases: detail lookup, location-based search, and global monitoring. However, it feels slightly thin as it lacks tools for broader queries (e.g., by date range or magnitude range without location) or additional data like tsunami alerts, which might be expected in this domain.

Completeness4/5

The tool set covers essential earthquake data retrieval: specific event details, local searches, and global recent events. Minor gaps exist, such as no tools for historical data beyond recent days, filtering by region without coordinates, or accessing related data like tectonic plate information, but agents can work around these with the provided tools.

Resources

Need Help?