Skip to main content
Glama

Usgs Earthquakes

by io.github.pipeworx-io

What Can I Ask Pipeworx?

suggest_questions
Read-onlyIdempotent

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

Schema Changelog

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

  1. Added

TDQS

A4.3/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 valuable behavioral context by explaining the output (category-bucketed example questions with tool+argument shapes), the source (live catalog), and the optional topic filtering. This goes beyond the annotations without contradicting them.

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 longer than many, but every sentence serves a purpose: example queries, the return type, the tool-source context, and usage instructions. It is front-loaded with practical questions and structured logically from purpose to invocation.

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

Completeness5/5

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

Given the tool's single optional parameter and no output schema, the description is fully complete: it explains what the tool does, when to use it, how to call it with or without arguments, and what the output contains. No important gaps remain.

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%, with a clear description for the optional `topic` parameter. The description reinforces the parameter meaning with examples ('finance', 'pharma', 'betting') and clarifies the no-argument behavior, but it adds only marginal value beyond what the schema already provides. Baseline 3 is appropriate.

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 the tool's function: an onboarding entry point that returns category-bucketed example questions with the exact tool and argument shape needed to answer them. It is specific about the resource (Pipeworx's live catalog) and distinguishes itself from siblings by framing itself as the 'FIRST' tool to use when unfamiliar with Pipeworx.

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?

The description explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you,' providing strong usage context. It also gives example queries and mentions that it can teach how to call meta-tools. However, it does not explicitly name alternate tools or state when not to use this tool, so it falls short of a 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 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