Skip to main content
Glama

Read current GDACS disaster alerts worldwide

disasters
Read-only

Current disaster alerts from GDACS (UN OCHA and EC JRC): type (earthquake, tropical cyclone, flood, volcano, drought, wildfire), name, country, alert level, start date, severity and link. Filter by type and alert level. Attribution: GDACS. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "disasters"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoEQ, TC, FL, VO, DR or WF (optional)
alertNogreen, orange or red (optional)
limitNo1 to 30 (default 10)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
eventsNo
sourceNo
checkedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value comes from the cost/payment model: $0.002 per successful call via x402 (USDC on Base, Solana and others) and failed calls are free. That is genuinely decision-relevant context an agent needs before calling. It stops short of disclosing refresh cadence or result volume behavior.

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?

Front-loaded with purpose and covered fields, then filters, then attribution and pricing in one trailing sentence. Every clause carries information; nothing is redundant with the title or schema.

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, the description needn't explain return values, and annotations cover the safety profile. Purpose, filterable dimensions, and cost are all covered. Only secondary details (data freshness, how limit interacts with alert levels) are left unstated.

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 coverage is 100%, so baseline would be 3, but the description earns more by expanding the opaque codes the schema lists: EQ, TC, FL, VO, DR, WF become earthquake, tropical cyclone, flood, volcano, drought, wildfire. That mapping is real meaning not present in the structured field.

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?

A specific verb+resource ('Current disaster alerts from GDACS') with the source spelled out (UN OCHA and EC JRC) and an enumeration of returned fields. It does not, however, differentiate itself from the sibling 'weather_alerts', so an agent comparing the two must infer the distinction from the source name alone.

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?

'Filter by type and alert level' implies how to narrow results, but there is no statement of when this tool is the right choice versus alternatives, nor any exclusions or prerequisites. Usage is inferable but not guided.

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.

Resources