Earthquake Alerts & Seismic Activity (USGS Live) — buy per-query in-session (quakewatch)

data_preview

Read-onlyIdempotent

✅ No API key needed — call this now. Listing: quakewatch: Earthquake Alerts (USGS M2.5+ 24h). Price 0.01 USDC/query (max 20 queries/session). Sample questions: Are there any significant earthquakes (M5+) in the last 24 hours?; What were the most recent earthquakes worldwide?. FREE preview — no key, no payment. Try one of the sample questions now.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: no API key required, free preview, 0.01 USDC/query for the underlying listing, and a 20-query session cap. It does not contradict the annotations.

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

Conciseness2/5

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

The description is bloated with repetition: 'No API key needed' appears twice, and 'FREE preview — no key, no payment' restates the opening. Emojis, exclamation marks, and repeated calls to act now make it feel like advertising rather than a concise tool specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is heavily tied to one specific listing (quakewatch) and does not explain general preview semantics, what the response will contain, or how this relates to paid sessions. With no output schema present, the description should clarify what the agent can expect to receive; it does not.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by providing concrete sample questions that demonstrate how the question parameter can be used, even though it does not mention the slug parameter at all.

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

Purpose3/5

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

The description suggests a free preview of the quakewatch data listing and includes sample questions, but it never states the core action with a clear verb-resource structure. It reads more like a promotional call-to-action than a tool definition, and the actual purpose is mostly supplied by the schema description ('Free, guest-callable taste of a listing').

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 repeatedly urges the agent to call the tool immediately but gives no guidance on when to prefer it over sibling tools such as data_session_query or data_session_open. There is no mention of the paid session workflow or when a preview is appropriate versus a real data query.

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

All Earthquake Alerts & Seismic Activity (USGS Live) — buy per-query in-session (quakewatch) 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

B3.3/5.0

Disambiguation2/5

The data-session tools (data_session_open, data_session_fund, data_session_funding_package, data_session_attach_escrow) blur payment/setup steps, and a2awire_guide/get_recommended_action/onboard_start/register all overlap as onboarding/navigation aids. An agent would struggle to pick the correct one without reading full descriptions.

Naming Consistency3/5

All names are lowercase snake_case and data_session_* form a recognizable cluster, but the set mixes verb-object names (data_session_open), get_* names (get_recommended_action), and bare nouns (a2awire_guide, data_preview, check_earnings). There is no single predictable convention across the server.

Tool Count3/5

Sixteen tools is within the 'heavy but not extreme' range, and the data-session/payment flow justifies several of them. Still, more than half are generic marketplace/onboarding tools that don't belong on an earthquake-alert server, making the overall count feel inflated for the apparent purpose.

Completeness3/5

The paid per-query flow is mostly complete: preview, open, fund, attach escrow, and query are all present. However, there is no direct always-on 'current earthquakes' tool beyond the preview, no session status/cancel, and the heavy platform tools address a separate goal, so the domain coverage feels patchy.

Resources

Need Help?