Skip to main content
Glama
INGV

mcp-fdsnws-event

Official
by INGV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fdsn_query_earthquakesA

Query earthquake events from an FDSN datacenter with flexible parameters.

Returns a compact tabular result (columns + rows), one row per event, using the preferred origin and magnitude. Depth is in KILOMETERS. For the full detail of a single event (all origins/magnitudes, arrivals, focal mechanism) use the by-id tools.

Common usage examples:

  • Recent events (today): {} (no parameters needed)

  • Significant events: {"minmag": 4.0, "starttime": "YYYY-MM-DDTHH:MM:SS"}

  • Geographic area: {"minlat": 41.0, "maxlat": 43.0, "minlon": 12.0, "maxlon": 15.0}

  • Radial search: {"latitude": 41.9, "longitude": 12.5, "maxradiuskm": 50}

  • Strongest first: {"orderby": "magnitude", "limit": 10}

  • Next page: {"offset": 101} (offset + returned_count from the previous call)

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

fdsn_get_earthquake_by_idA

Get basic information about a specific earthquake event by event ID.

Returns the preferred origin, preferred magnitude, station magnitudes, and amplitudes. For detailed data (all alternative origins, all alternative magnitudes, or seismic arrivals/picks), use the specialized tools instead.

The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values.

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

fdsn_get_arrivals_by_idA

Get all seismic phase arrivals for an earthquake event, including linked pick data (station, time, phase). Use this when asked about recorded phases, station readings, or seismic wave arrivals.

The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values.

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

fdsn_get_allmagnitudes_by_idA

Get all computed magnitude solutions for an earthquake event. Use this when asked about different magnitude types (ML, Mw, Mb, Md), magnitude comparisons across agencies, or station counts.

The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values.

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

fdsn_get_allorigins_by_idA

Get all computed origin solutions (hypocenter locations) for an earthquake event. Use this when asked about alternative locations, origin comparisons, or which agencies computed origins.

The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values.

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

fdsn_get_focalmechanism_by_idA

Get focal mechanism and moment tensor data for an earthquake event. Returns nodal planes (strike, dip, rake), principal axes (T, P, N), and moment tensor components when available. Use this for understanding the rupture geometry and seismic source characteristics.

The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values.

Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct aspect of FDSN earthquake data: querying events, fetching basic info, and retrieving specific data types (arrivals, magnitudes, origins, focal mechanisms). There is no overlap or ambiguity between the tools.

Naming Consistency4/5

The tools follow a clear fdsn_<action>_<resource> pattern, with consistent use of '_by_id' for detail retrieval. Minor deviations include the mix of 'query' for search versus 'get' for retrieval, and singular/plural resource names (e.g., earthquakes vs earthquake), but the pattern remains predictable.

Tool Count5/5

With 6 tools, the set is well-scoped for an FDSN event server. It provides a search tool and targeted detail tools without unnecessary redundancy, making it easy for agents to navigate.

Completeness5/5

The tool surface covers the full lifecycle of earthquake event exploration: searching, getting summary details, and retrieving all major data products (origins, magnitudes, arrivals, focal mechanisms). No critical operations are missing for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources