Skip to main content
Glama

Emsc

by io.github.pipeworx-io

Search Earthquakes

search_earthquakes
Read-onlyIdempotent

Search seismic events from EMSC (European-Mediterranean Seismological Centre) via the FDSN-standard seismicportal.eu API. Global coverage with especially strong Europe/Mediterranean reporting — complements USGS. Filter by UTC time range, magnitude, and location (either a bounding box OR a center point + radius in degrees). Times are UTC ISO 8601, depth in km, and place names come from the Flynn-Engdahl region. Example: search_earthquakes({ start: "2026-01-01", end: "2026-02-01", minmag: 5.0, orderby: "magnitude" }) or search_earthquakes({ lat: 38.0, lon: 23.7, maxradius: 5, minmag: 3 }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd of UTC time window, ISO 8601.
latNoCenter latitude for circular search (use with lon + maxradius).
lonNoCenter longitude for circular search (use with lat + maxradius).
limitNoMaximum number of results, 1-1000 (default: 50).
startNoStart of UTC time window, ISO 8601 (e.g. "2026-01-01" or "2026-01-01T00:00:00").
maxlatNoBounding box northern latitude, -90 to 90 (optional).
maxlonNoBounding box eastern longitude, -180 to 180 (optional).
maxmagNoMaximum magnitude (optional).
minlatNoBounding box southern latitude, -90 to 90 (optional).
minlonNoBounding box western longitude, -180 to 180 (optional).
minmagNoMinimum magnitude (optional).
orderbyNoResult ordering (default: "time", i.e. newest first).
maxradiusNoMaximum radius in degrees from center lat/lon (optional).
minradiusNoMinimum radius in degrees from center lat/lon (optional).

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: +[
+  {
+    "end": "2026-02-01",
+    "minmag": 5,
+    "orderby": "magnitude",
+    "start": "2026-01-01"
+  },
+  {
+    "lat": 38,
+    "limit": 100,
+    "lon": 23.7,
+    "maxradius": 5,
+    "minmag": 3
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, so safety profile is clear. The description adds valuable context about the data source (EMSC, FDSN API), regional strengths, and parameter interactions (bounding box vs circle), but does not contradict annotations.

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 efficiently structured: purpose in first sentence, then clear bullet-like enumeration of filter types, followed by examples. Every sentence adds value without redundancy.

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 14 parameters, no required ones, and no output schema, the description provides sufficient context for correct invocation: it explains the two location search modes, time range format, magnitude limits, ordering options, and provides examples. It also mentions the API source and regional coverage.

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?

Schema coverage is 100%, and the description adds meaningful context beyond parameter names and types: it explains the coordinate system (Flynn-Engdahl region), units (depth in km, radius in degrees), and provides two concrete usage examples showing different parameter combinations.

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 it searches seismic events from EMSC via FDSN-standard API, with global coverage but special emphasis on Europe/Mediterranean. It distinguishes itself from sibling 'recent_earthquakes' by mentioning complements USGS and providing extensive filtering options.

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 provides clear context on when to use the tool (for historical or filtered earthquake data) and includes explicit examples. However, it does not explicitly contrast with sibling 'recent_earthquakes' or provide 'when not to use' 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