DaedalMap Tsunami Data
Server Details
Global tsunami events from NOAA NCEI, 2000 BC-present: wave height, runups, and counts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- xyver/daedal-map
- GitHub Stars
- 3
- Server Listing
- daedal-map
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 6 of 6 tools scored.
There is notable overlap between 'get_disaster_link_chain' and 'get_disaster_links_for_event' – both require an exact event ID and return related disaster information, with descriptions that do not fully clarify the distinction. Other tools are clearly distinct.
Most tools use the 'get_' prefix consistently (5 out of 6), with one exception: 'search_disaster_links'. The pattern is mostly uniform and readable.
With 6 tools, the server is well-scoped for its domain – covering catalog discovery, pack metadata, tsunami queries, and link exploration without being excessive or sparse.
Core workflows (discovering packs, querying tsunami events, exploring links) are covered. A minor gap is the lack of a tool to retrieve a single tsunami event's details by ID, but the query tool likely provides event IDs for link tools.
Available Tools
6 toolsget_catalogGet CatalogRead-onlyInspect
Free discovery. Returns the list of live agent-ready data packs available on DaedalMap.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_disaster_link_chainGet Disaster Link ChainRead-onlyInspect
Free linked-disaster helper. Expands one exact disaster event id into a bounded related-event chain. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | Maximum link-chain depth to traverse. Default 1. | |
| pack_id | No | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. | |
| event_id | Yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| cross_type_only | No | When true, only return cross-hazard links. Default true. |
get_disaster_links_for_eventGet Disaster Links For EventRead-onlyInspect
Free linked-disaster helper. Resolves one exact disaster event id into its published related-disaster links. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.
| Name | Required | Description | Default |
|---|---|---|---|
| pack_id | No | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. | |
| event_id | Yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| cross_type_only | No | When true, only return cross-hazard links. Default true. |
get_packGet PackRead-onlyInspect
Free discovery. Returns detailed metadata, coverage, freshness, preferred canonical tool guidance, and first-query examples for one pack. Call this before querying a new pack so you can see time shape, coverage limits, and the paste-ready first query.
| Name | Required | Description | Default |
|---|---|---|---|
| pack_id | Yes | Pack identifier such as 'currency', 'earthquakes', 'floods', 'hurricanes', 'tornadoes', 'tsunamis', 'un_sdg', 'volcanoes', 'world_factbook', or 'worldpop'. |
get_tsunami_eventsGet Tsunami EventsRead-onlyInspect
Paid x402 canonical tool. Queries tsunamis_events for historical tsunami records and water-height/runup metrics. Best for event counts, max water height thresholds, and top-event lookups. Region filters may use ISO3 country ids or reviewed named-water loc_ids such as IHO1953-240001002 for the Mediterranean Sea; XOO is deprecated. Call without payment first - the server returns HTTP 402 with the exact USDC price before any charge.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Optional sort instructions for row-returning queries. | |
| limit | No | Maximum number of rows to return. For largest-wave or latest-event requests, include a narrow time range or region_ids before sorting. | |
| output | No | Optional output controls such as response format hints. | |
| filters | Yes | Structured filters including time ranges, region_ids, and compare clauses. Tsunami queries commonly use year-style windows and may use geometry-backed ocean/sea ids such as XSM. | |
| metrics | Yes | Metric ids to return, such as 'event_count', 'max_water_height_m', or event attributes. | |
| request_id | No | Optional caller-supplied request id for tracing and idempotency. |
search_disaster_linksSearch Disaster LinksRead-onlyInspect
Free linked-disaster discovery helper. Searches published cross-disaster link families by event-type direction, optional via-event type, and optional year window. Use this when you want to discover whether a relationship family exists before you have an exact event id.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of matching chains to return. Default 10. | |
| year_end | No | Optional inclusive ending year filter. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| year_start | No | Optional inclusive starting year filter. | |
| end_event_type | No | Optional ending event type such as tsunami, flood, tornado, or earthquake. | |
| via_event_type | No | Optional intermediate event type for bounded chain discovery. | |
| start_event_type | No | Optional starting event type such as earthquake, hurricane, volcano, wildfire, flood, tornado, or tsunami. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.