Skip to main content
Glama
mysukriramli

disaster-wire

by mysukriramli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_disaster_by_id

Read-onlyIdempotent

Retrieve telemetry, impact metrics, casualty estimates, and exposed infrastructure for a known disaster event ID. Use as a read-only lookup only when you already have a valid event_id.

Instructions

Retrieve comprehensive technical telemetry, impact metrics, casualty estimates, and exposed infrastructure for a specific disaster ID. Use exclusively when you already hold a valid event_id obtained from list_active_disasters or find_disasters_near_coordinates. Do not use to browse or discover active disasters (use list_active_disasters instead) or for coordinate proximity queries (use find_disasters_near_coordinates instead). Pure read-only lookup. If the requested event_id is not in the active pool, returns an {'error': '...'} JSON object without raising exceptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesUnique incident identifier string (e.g., 'usgs_nc75001234', 'gdacs_1002341', or 'news_e5f6g7h8').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / event_id / description
      Added value: +"Unique incident identifier string (e.g., 'usgs_nc75001234', 'gdacs_1002341', or 'news_e5f6g7h8')."
    • removedInput schema / properties / event_id / title
      Removed value: -"Event Id"
    • removedInput schema / title
      Removed value: -"get_disaster_by_idArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_disaster_by_idOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond those annotations by stating that an inactive or unknown event_id returns an error JSON object without raising exceptions.

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 front-loaded with the tool's purpose, then moves efficiently through usage constraints, exclusions, alternatives, and error behavior. There is no filler or repetition that detracts from the key guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only lookup with no output schema, the description is complete enough: it covers what data is returned, how to obtain a valid event_id, when not to use the tool, and how errors are surfaced. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the event_id type and examples are already documented. The description adds meaningful semantics by requiring a valid event_id obtained from the sibling tools and by clarifying the active-pool constraint and error behavior for invalid IDs.

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 uses a specific verb, 'Retrieve,' and names the exact resource, a disaster by event_id. It also distinguishes the tool from both siblings by naming list_active_disasters and find_disasters_near_coordinates as alternatives for browsing and proximity queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: only when the caller already holds a valid event_id from list_active_disasters or find_disasters_near_coordinates. It also gives clear when-not-to-use cases for browsing and coordinate proximity queries, naming the correct sibling in each case.

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

Deploy Server

Other Tools