Skip to main content
Glama

Disasters worldwide: current Orange and Red GDACS alerts (UN + European Commission)

get_disasters
Read-only

Free. Current GDACS events with an Orange or Red alert, split into fast events (earthquakes, tropical cyclones, floods, volcanoes, wildfires) and slow droughts with how many days they have lasted: type, alert level, name, affected countries, start date, severity text, GDACS report link. Automatic impact alerts, not official warnings and not forecasts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_disasters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-safety and openness, so the description's added value is in data provenance and limitations: 'Free', 'Automatic impact alerts, not official warnings and not forecasts'. The not-a-warning / not-a-forecast caveat is exactly the kind of context an agent needs before relaying this data. It does not state update cadence or how far back events are retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense block that front-loads the key scope (Orange/Red GDACS alerts) and then the fast-vs-slow split. Nothing is filler, though the run-on clause stacking field names makes it slightly harder to parse at a glance than short separate sentences would.

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 no parameters and no output schema, the description carries the return-value burden and does so by listing the fields delivered (type, alert level, name, countries, start date, severity, report link). The fast/slow drought distinction with 'days lasted' is a genuinely tool-specific detail. Missing only freshness/update cadence and approximate result volume.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly presents this as an unfiltered feed with no arguments, and the enumerated return fields serve the role parameter docs normally would.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: 'Current GDACS events with an Orange or Red alert', broken out into fast events and slow droughts, with the returned fields enumerated. An agent can tell this is a multi-hazard disaster feed rather than a single-hazard one. It stops short of naming a sibling (e.g. get_earthquakes or get_flood_warnings) as the narrower alternative, which would have made the differentiation explicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'Current' plus 'Orange or Red alert' signals a live-alert feed, and the closing note scopes it to automatic impact alerts rather than forecasts. There is no explicit when-to-use or when-not-to-use instruction, and no pointer to the single-hazard siblings that would be better for a targeted earthquake or flood query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.