Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

by com.daedalmap

Get Live Earthquake Events

get_live_earthquake_events
Read-only

Free live wrapper. Calls the USGS FDSN API for recent preliminary earthquake events normalized to DaedalMap event fields. Use this only when the caller explicitly wants live/preliminary upstream results or needs a very recent window not yet present in the published canonical earthquake lane. This is not the enriched canonical history lane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoRecent lookback window in hours. Ignored when start_time is provided.
limitNoMaximum live rows to return.
orderbyNoUSGS result ordering.
end_timeNoOptional exclusive-ish ISO-8601 end datetime. Defaults to now.
request_idNoOptional caller-supplied request id for tracing.
start_timeNoOptional inclusive ISO-8601 start datetime.
max_latitudeNoOptional bounding box maximum latitude.
min_latitudeNoOptional bounding box minimum latitude.
max_longitudeNoOptional bounding box maximum longitude.
min_longitudeNoOptional bounding box minimum longitude.
min_magnitudeNoMinimum earthquake magnitude. Defaults to 2.5.

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true. The description adds that it calls the USGS API and normalizes to DaedalMap event fields. This is useful context but does not significantly expand beyond what the annotation already conveys. No contradictions.

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 three sentences, front-loaded with the main purpose, and every sentence serves a clear role. It is concise and well-structured.

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?

The description, combined with the schema and annotations, provides sufficient context for a read-only tool with 11 well-described parameters. It explains the source and normalization, and the usage guidance is clear. Lacks details on output format, but that may be covered by the DaedalMap event field standard.

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%, so the baseline is 3. The description does not add any additional parameter information beyond what is already in the schema; it relies on the schema's descriptions.

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 that this tool retrieves live/preliminary earthquake events from the USGS FDSN API and normalizes them. It explicitly distinguishes itself from the canonical earthquake lane, making the purpose specific and unambiguous.

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 explicitly tells when to use this tool (when live/preliminary results are needed or for a very recent window) and what it is not (the enriched canonical history lane). Although it does not name the alternative, the sibling tool get_earthquake_events is implied as the canonical one.

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

All DaedalMap Disaster and Geospatial Data 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

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct scopes with detailed 'Use this' guidance, but a few pairs like get_disaster_link_chain and get_disaster_links_for_event, or query_dataset versus the specialized get_* event tools, could cause momentary confusion. Overall, descriptions mitigate overlap well.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (check_, compare_, convert_, create_, estimate_, get_, list_, resolve_). Minor exceptions like loc_id_info and query_dataset are acceptable but break the pattern slightly.

Tool Count3/5

28 tools exceed the preferred range, but the broad domain spanning disasters, geospatial geometry, reference conversion, and export jobs justifies many of them. Still, the count feels heavy and might overwhelm agents.

Completeness5/5

The tool surface is remarkably comprehensive: discovery (catalog, pack, geometry catalog), resolution (point, reference, scope), geometry (check, get, compare), conversion (quote, create, status), and disaster events for multiple types. No critical dead ends for the stated domain.

Resources