Skip to main content
Glama
Sign In
Globalpulse-MCP

Globalpulse-MCP

by gpavan1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GDACS — Active Global Disasters

globalpulse_disasters_get_active
Read-only

Retrieve active disaster alerts from the UN GDACS system, covering earthquakes, cyclones, floods, volcanoes, droughts, and wildfires. Filter by event type and alert level.

Instructions

Live disaster alerts from the UN GDACS system. Earthquakes, cyclones, floods, volcanoes, droughts, wildfires. Alert levels: Green (watch), Orange (warning), Red (severe). Args: event_type ("all","EQ","TC","FL","VO","DR","WF"), alert_level ("all","Green","Orange","Red"), limit, response_format

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

Input Schema

NameRequiredDescriptionDefault
limitNo
event_typeNoall
alert_levelNoall
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already show readOnlyHint, openWorldHint. Description adds context on alert levels but doesn't disclose any behavioral traits beyond what annotations provide.

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?

Concisely covers tool purpose, supported event types, alert levels, and parameters in a few sentences. Could be more structured but no wasted words.

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?

Adequately explains the tool's purpose and parameters. Without an output schema, describing the return format would improve completeness, but current description is sufficient for understanding.

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?

Despite 0% schema description coverage, the description lists all parameters with allowed enum values, adding meaning beyond the schema alone. However, 'limit' and 'response_format' are only named without details.

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?

Clearly states it provides live disaster alerts from the UN GDACS system, listing disaster types and alert levels. Distinguishes from sibling 'globalpulse_disasters_get_by_country' by focusing on global active alerts.

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?

Implied use for accessing global active alerts, but no explicit guidance on when to use this tool over siblings like the country-specific one.

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