DaedalMap Tornado Events

Get Event

get_event

Read-onlyIdempotent

Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable event_id first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Per-section ceiling for relationships, affected places, observations, or geometry frames.
`include`	No	Optional companion layers. Omit for the lightweight event summary. Geometry is never returned implicitly.
`pack_id`	Yes	Required disaster pack_id that returned this event_id from get_data. The tool never searches other packs.
`event_id`	Yes	Exact stable event_id returned by a disaster-pack get_data row.
`source_id`	Yes	Required source_id from the same get_data result. Must identify one published event source in pack_id.
`request_id`	No	Optional caller-supplied request id for tracing.
`geometry_mode`	No	current returns the representative/current shape; timeline returns bounded progression frames where supported.	current
`relationship_depth`	No	Bounded cross-hazard traversal depth when relationships is included.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`event`	No
`reason`	No
`pack_id`	No
`event_id`	No
`geometry`	No
`guidance`	No
`included`	No
`warnings`	No
`available`	No
`next_step`	No
`source_id`	No
`event_type`	No
`next_steps`	No
`provenance`	No
`request_id`	No
`observations`	No
`schema_class`	No
`clarification`	No
`relationships`	No
`affected_places`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

changedInput schema / properties / pack_id / description

Previous value: -"Optional disaster pack hint. Recommended when known to avoid probing unrelated event sources."New value: +"Required disaster pack_id that returned this event_id from get_data. The tool never searches other packs."

addedInput schema / properties / pack_id / minLength
```
Added value: +1
```

addedInput schema / properties / source_id

Added value: +{
+  "description": "Required source_id from the same get_data result. Must identify one published event source in pack_id.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "event_id"
-]New value: +[
+  "pack_id",
+  "source_id",
+  "event_id"
+]

AddedSep 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety burden is lifted. The description adds genuinely useful behavioral context on top: retrieval is limited to a single exact event and only the layers 'explicitly requested' are attached, reinforcing the opt-in nature of the include set.

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?

Two sentences, zero filler, and the core action is front-loaded before the prerequisite. Every clause carries information the agent needs.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover the safety profile. The description supplies the critical precondition (a stable event_id from get_data) and the opt-in layer model, leaving little an agent would need to know before calling.

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 parameters like include, geometry_mode, relationship_depth and limit are already fully documented with defaults and bounds. The description restates the four include values but adds no format or interaction detail beyond the schema, making the baseline 3 correct.

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?

Specific verb (Retrieve) plus a narrowly scoped resource ('one exact disaster event'), and it enumerates the optional companion layers. It also distinguishes itself from the sibling it depends on by naming get_data as the source of the event_id, so an agent can tell the two apart without opening either schema.

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?

'Use get_data to obtain the stable event_id first' gives an explicit prerequisite and routes the agent to the correct sibling for the lookup step. It stops short of stating when NOT to use this tool (e.g. bulk/multi-event retrieval), so it is clear context rather than full when/when-not guidance.

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

All DaedalMap Tornado Events tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.