Skip to main content
Glama
lzinga

US Government Open Data MCP

usgs_earthquakes

Read-only

Search for earthquakes by magnitude, location, and date range. Retrieve depth, alert level, tsunami risk, and felt reports.

Instructions

Search for earthquakes by magnitude, location, date range, and more. Returns magnitude, location, depth, time, alert level, tsunami risk, and felt reports. Magnitude scale: 2.5+ felt by people, 4.0+ moderate, 5.0+ significant, 7.0+ major.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
starttimeNoStart date ISO format: '2024-01-01'
endtimeNoEnd date ISO format: '2024-12-31'
minmagnitudeNoMinimum magnitude (e.g. 4.0, 5.0, 6.0)
maxmagnitudeNoMaximum magnitude
latitudeNoCenter latitude for radius search
longitudeNoCenter longitude for radius search
maxradiuskmNoSearch radius in km (requires lat/lon)
alertlevelNoPAGER alert level: 'green' (Limited impact — no damage expected), 'yellow' (Regional impact — some damage possible), 'orange' (National/international impact — significant damage likely), 'red' (Massive impact — extensive damage and casualties expected)
limitNoMax results (default 20, max 200)
orderbyNoSort order (default: time)
Behavior4/5

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

Discloses return fields (magnitude, location, depth, time, alert level, tsunami risk, felt reports) and magnitude scale interpretation, adding value beyond readOnlyHint annotation.

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?

Three concise sentences with key information front-loaded. No wasted words.

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?

Given 10 parameters and no output schema, the description covers typical output and magnitude scale well. Lacks details on pagination or defaults but is fairly complete for a search tool.

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 100% with descriptions for all parameters. Description adds magnitude scale interpretation but does not enhance individual parameter understanding significantly.

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?

Clearly states it searches for earthquakes by various criteria. However, does not differentiate from sibling tools usgs_earthquake_count or usgs_significant.

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?

No explicit guidance on when to use this tool vs alternatives. Does not mention when not to use or provide context for alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lzinga/us-gov-open-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server