Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

monitor_global_seismic_events

Read-onlyIdempotent

Monitor real-time global and regional earthquake events with Richter magnitudes, hypocenter depths, epicenters, and tsunami alerts from USGS, EMSC, and AFAD seismic networks via a single feed.

Instructions

Monitor real-time global and regional earthquake events, Richter magnitudes, hypocenter depths, epicenters, and tsunami alerts across USGS, EMSC (Euro-Med), and AFAD seismic networks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "network": "<network>"
    },
    "name": "monitor_global_seismic_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYesSeismic authority feed: multi_network_global (USGS + EMSC + AFAD cross-verified), emsc_euro_med (European-Mediterranean), or afad_turkey (AFAD official feed).multi_network_global
maxResultsNoMaximum number of seismic events to return.
minMagnitudeNoMinimum earthquake Richter magnitude threshold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior; the description adds that data is real-time and lists event attributes and tsunami alerts. It does not disclose rate limits, latency, pagination, or response format, so it adds context but not rich behavioral detail.

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?

A single front-loaded sentence with no filler; each phrase contributes scope, event attributes, or source networks. The density is appropriate for a concise one-sentence definition.

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?

For a three-parameter read-only tool with full schema documentation and rich annotations, the description supplies key scope: real-time events, regions, seismic networks, and included attributes. Return format and rate limits remain unspecified, but these are less critical given the schema and annotations.

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%, and the schema fully documents the network enum, maxResults, and minMagnitude. The description adds no parameter-specific semantics beyond noting global and regional scope and source networks, so the baseline 3 applies.

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 gives a specific verb ('monitor') and resource ('earthquake events') and scopes it to real-time global and regional data across named seismic networks. It is clearly distinguishable from all listed sibling tools, which cover unrelated domains.

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?

It implies use for real-time earthquake monitoring and names the data networks, but gives no explicit when-to-use or when-not-to-use guidance and no alternatives. Because no sibling covers the same domain, this is adequate but minimal.

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