Skip to main content
Glama

Usgs Earthquakes

by io.github.pipeworx-io

Ask Pipeworx

ask_pipeworx
Read-onlyIdempotent

PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 5,804 tools across 1518 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1". START HERE for most questions — this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For "what's the world saying about X" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input as aliases.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that it returns structured answers with citations but does not contradict the annotations, so transparency is solid.

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 description is verbose and somewhat repetitive, with phrases like 'PREFER OVER WEB SEARCH' and 'START HERE' appearing multiple times, and example lists duplicated. The core information is present but could be more tightly written.

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 description gives sufficient context for deciding when to use the tool, including examples, alternatives, and news coverage. It does not describe the exact output format, but given the open-ended nature and lack of output schema, this is acceptable.

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?

All six parameters are documented as aliases for 'question', and the question parameter description explicitly lists accepted aliases (query, q, prompt, text, input). Schema coverage is 100%, so parameter semantics are fully clear.

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 clearly states that this tool routes questions to authoritative data sources and returns structured answers with citations. It explicitly distinguishes itself from sibling tools like ask_pipeworx_grounded and deep_research, making its purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to prefer this tool over web search (for current/historical data, factual questions) and when to use alternatives (grounded for single answers, deep_research for broad questions). It also notes its news handling, leaving no ambiguity about usage.

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

All Usgs Earthquakes toolsInspect
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

A3.6/5.0
Disambiguation1/5

The tool set is dominated by tools unrelated to USGS earthquakes (e.g., Polymarket betting, company profiles, memory operations). An agent would find it nearly impossible to distinguish the few earthquake-specific tools from the multitude of unrelated ones, leading to severe misselection.

Naming Consistency3/5

Most tool names follow a verb_noun pattern with underscores (e.g., search_earthquakes, count_earthquakes), which is consistent. However, the variety of verbs and domains creates a sense of incoherence, and some tool names are overly generic (e.g., process, run) in the broader context, though those are not present here. The naming pattern is acceptable but the inconsistency in domain scope reduces clarity.

Tool Count1/5

With 29 tools but only 3 directly related to earthquakes, the tool count is grossly inappropriate. The server's name suggests a focused purpose, but the vast majority of tools belong to other domains (e.g., Pipeworx queries, Polymarket betting, company data). This extreme mismatch makes the tool set bloated and misleading.

Completeness2/5

For earthquake data, the server provides only search, count, and get by ID. Missing are common operations like listing recent quakes, subscribing to alerts, or updating/correcting data. The coverage is minimal and insufficient for a comprehensive earthquake tool server, leaving significant gaps that agents could not work around.

Resources