Skip to main content
Glama

Emsc

by io.github.pipeworx-io

Recent Earthquakes

recent_earthquakes
Read-onlyIdempotent

Get recent earthquakes from EMSC (European-Mediterranean Seismological Centre): the last N days above a minimum magnitude, newest first. Convenience wrapper over the FDSN event API. Global coverage, strong in Europe/Mediterranean. Times are UTC ISO 8601, depth in km. Example: recent_earthquakes({ days: 7, minmag: 4 }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days back to look (default: 7).
limitNoMaximum number of results, 1-1000 (default: 50).
minmagNoMinimum magnitude to include (default: 4).

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 7,
+    "minmag": 4
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive. Description adds useful details: times in UTC ISO 8601, depth in km, and an example call. No contradiction with annotations. Does not mention rate limits or data freshness, but sufficient for a read-only tool.

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 no waste. Front-loaded with action and key details. Every sentence adds value: source, parameters, example, geographic scope, output format.

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 no output schema, description explains output format (UTC ISO 8601, depth in km). Covers parameter defaults (days=7, minmag=4, limit=50 from schema), geographic coverage, and example. Sufficient for agent to understand and use tool correctly.

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?

All three parameters are described in the input schema with default values (schema coverage 100%). Description restates 'last N days above a minimum magnitude' and provides an example, but does not add significant meaning beyond schema. 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?

Clearly states it gets recent earthquakes from EMSC with parameters days and minmag, newest first. Distinguishes from sibling 'search_earthquakes' by being a convenience wrapper for recent events. Specifies verb 'get', resource 'earthquakes from EMSC', and scope 'last N days above minimum magnitude'.

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

Usage Guidelines3/5

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

Indicates when to use (get recent earthquakes) and provides context on geographic coverage (global but strong in Europe/Mediterranean). However, does not explicitly state when not to use or how it differs from sibling 'search_earthquakes'. Lacks direct alternative guidance.

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

All Emsc 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

A4/5.0
Disambiguation3/5

Multiple tools overlap: ask_pipeworx and ask_pipeworx_beta are currently identical, and the five prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker) cover adjacent tasks that require careful reading. However, descriptions are unusually explicit about when to prefer each, and non-overlapping domains (memory, subscriptions, earthquakes, npm) are clearly separated.

Naming Consistency4/5

All tool names are snake_case with a mostly verb-first pattern (ask_, compare_, discover_, generate_, list_, scan_, search_, validate_), making the surface predictable. Minor deviations like deep_research, entity_profile, and single-word verbs (remember, recall, forget) break the pattern slightly, but each family is internally consistent.

Tool Count2/5

33 tools exceeds the 25+ threshold for 'too many,' and several could be consolidated — ask_pipeworx_beta is redundant today, and the prediction-market suite could fold into 2-3 tools. The count reflects a genuinely wide data platform with meta-tools (discover_tools, suggest_questions, ask_pipeworx) already covering discovery, so the surface feels heavy for an agent to triage.

Completeness4/5

Core workflows are well covered: querying (ask_pipeworx, grounded, deep_research), research profiles (entity_profile, compare_entities, recent_changes), input resolution (resolve_entity), fact-checking (validate_claim), memory lifecycle, and subscription lifecycle all have complete loops. Minor gaps exist, notably no tool to fetch a pipeworx:// citation URI directly (search_within expects already-fetched text), and some one-off tools like generate_llms_txt and scan_dependency feel bolted on.

Resources