DaedalMap Wildfire 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pack_id": "<pack_id>",
      "source_id": "<source_id>",
      "event_id": "<event_id>"
    },
    "name": "get_event"
  }
}

Input 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

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the important behavioral fact that only explicitly requested layers are returned, which tells the agent results are opt-in rather than automatic; the 'never returns geometry implicitly' rule lives in the schema rather than the prose.

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, front-loaded with the operation and followed immediately by the prerequisite. Nothing is redundant or padded.

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?

With an output schema present and full parameter documentation, the description only needs to carry the operation and the prerequisite chain, both of which it does. The remaining detail an agent might want, such as per-layer return shape, is legitimately delegated to the output schema.

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% and every parameter already carries a detailed description, including pack_id scoping, include semantics, and geometry_mode. The description adds little beyond restating that layers are explicitly requested, so baseline 3 applies.

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?

States a specific verb and resource ('Retrieve one exact disaster event') plus the opt-in companion layers it can return, and it implicitly distinguishes itself from get_data by positioning that sibling as the discovery step. An agent can tell what it gets back without opening the 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?

Explicitly names the prerequisite path: get_data must be called first to obtain the stable event_id, which is the main routing decision between these two siblings. It stops short of an explicit when-not clause, but the sequencing guidance is unambiguous.

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

All DaedalMap Wildfire 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.