CEV-OS Data API

Hazard alerts (GDACS, tsunami, NAVAREA, USGS)

get_hazard_alerts

Read-onlyIdempotent

Use this when you need current natural-hazard alerts coarsened to country or NAVAREA region: GDACS, NOAA tsunami, NGA maritime warnings and USGS earthquakes. Free. License: cleared_with_attribution. Attribution required: GDACS, Global Disaster Alert and Coordination System, EC-JRC / UN OCHA (https://www.gdacs.org/). GDACS alerts are automatic estimates. Not for life-safety use; follow official national authorities. NOAA / NWS Tsunami Warning Centers (https://www.tsunami.gov/). NGA Maritime Safety Information (https://msi.nga.mil/). Not for navigation. U.S. Geological Survey (https://earthquake.usgs.gov/); credit requested.

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_hazard_alerts"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Case-insensitive substring on NAVAREA / tsunami center / country name, e.g. NAVAREA IV.
`country`	No	ISO 3166-1 alpha-2 country filter.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, yet the description still adds meaningful context: cost ('Free'), license tier, mandatory attribution per source, and the caveat that GDACS figures are automatic estimates. It does not disclose refresh cadence or whether results are cached, which would complete the behavioral picture.

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

Conciseness3/5

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

The usage sentence is front-loaded and efficient, but roughly half the text is license/attribution boilerplate with four URLs and repeated credit lines, which dilutes the operational signal. It is not padded with filler, yet the legal block crowds out more useful information like return shape.

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

Completeness3/5

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

For a simple two-optional-parameter read tool that already has full annotations and complete schema coverage, the missing piece is the result surface: with no output schema, the description never says what an alert record contains or how regions are keyed across the four sources. Source provenance and safety caveats are well covered.

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%, so both filters are fully documented in structured fields and baseline is 3. The description's mention of 'coarsened to country or NAVAREA region' only loosely reinforces what the region and country properties already state, adding no syntax or matching rules beyond the schema.

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?

Names a specific verb+resource ('current natural-hazard alerts') and enumerates the four underlying feeds (GDACS, NOAA tsunami, NGA maritime, USGS). The phrase 'coarsened to country or NAVAREA region' distinguishes it in granularity from the more event-level sibling get_natural_events, but no sibling is named explicitly.

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?

The opening clause gives a clear when-to-use condition, and 'Not for life-safety use' plus 'Not for navigation' carve out prohibited uses. It stops short of routing the agent to alternatives such as get_natural_events or get_severe_weather, so the selection logic among siblings is only implicit.

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

All CEV-OS Data API 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.

Resources

Need Help?