Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

earthquake_monitor_usgs_emsc_afad

Read-onlyIdempotent

Earthquake Monitor - USGS, EMSC & AFAD Multi-Network: Real-time structured data extraction feed for Earthquake Monitor - USGS, EMSC & AFAD Multi-Network.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "earthquake_monitor_usgs_emsc_afad"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description contributes one useful signal in "Real-time" (freshness), but says nothing about aggregation or de-duplication across three networks, coverage windows, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the single sentence is circular — the resource name appears twice with a contentless middle phrase. It is brief without being informative, so length is not earning its place.

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

Completeness2/5

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

With no output schema, the description carries the burden of explaining return values, yet it never describes record shape or what the multi-network merge yields. For an agent to call this correctly it needs to know at minimum that results are earthquake events across three contributing networks.

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?

Only one optional parameter (maxResults) exists and schema coverage is 100%, so the schema fully documents it. The description adds no meaning beyond it, but the high-coverage baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Real-time structured data extraction feed for Earthquake Monitor - USGS, EMSC & AFAD Multi-Network" restates the title verbatim and adds only the vague phrase "structured data extraction feed." It never says what the tool actually returns (earthquake events with magnitude, location, time, depth) or how it differs from the sibling per-network feeds like europe_mediterranean_earthquakes_emsc_official_data.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no condition for choosing this multi-network aggregate over the EMSC-only or AFAD-only siblings, and no exclusions. The only implied cue is "real-time," which the agent must infer rather than being told.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources