DaedalMap Tornado Events
Server Details
US tornado events 1950-present from the NOAA Storm Prediction Center: EF rating, tracks, damage.
- 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/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: catalog listing, pack metadata retrieval, dataset querying, and disaster link searching. No overlap in functionality.
All tool names follow a consistent 'verb_noun' pattern using lowercase with underscores (e.g., get_catalog, search_disaster_links). No mixing of conventions.
4 tools is slightly lean but reasonable for a focused gateway server. The count supports the server's apparent role as a data discovery and access layer.
Despite the server name 'Tornado Events', there are no tornado-specific tools. The generic catalog and query tools cover many datasets, but core tornado operations (e.g., listing events, getting details) are missing, leading to significant gaps.
Available Tools
4 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_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'. |
query_datasetQuery DatasetRead-onlyInspect
Generic structured query for direct source_id or pack_id access using the same contract as POST /api/v1/query/dataset. Free packs: boundaries, currency, distributed_manufacturing, floods, geography, nri, owid, reverse-geocoding, un_sdg, un_wpp, volcanoes, world_bank_wdi. Paid packs: earthquakes, hurricanes, tornadoes, tsunamis, wildfires, world_factbook, worldpop (x402 Base USDC).
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Optional sort instructions for row-returning queries. | |
| limit | No | Maximum number of rows to return for the requested source or pack. | |
| output | No | Optional output controls such as response format hints. | |
| filters | No | Structured filters including time, region_ids, and compare clauses. | |
| metrics | No | Metric ids to return. Use event_count for aggregate counts when supported. | |
| pack_id | No | Pack identifier such as 'currency', 'earthquakes', 'floods', 'hurricanes', 'tornadoes', 'tsunamis', 'un_sdg', 'volcanoes', 'world_factbook', or 'worldpop'. | |
| source_id | No | Concrete source id such as 'earthquakes_events', 'volcanoes_events', 'hurricanes_events', or 'un_sdg/01'. | |
| 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.