SeaWeb

get_disruptions

Read-onlyIdempotent

Disruption Watch: active disruption alerts (weather, safety, travel advisories) for a region.

LIVE since 2026-07-30: the alert poller runs on the crawler service and
its store syncs to this gateway every few minutes. Coverage is partial
and worth stating plainly: the weather feed is api.weather.gov, which is
UNITED STATES ONLY, and the advisory feed is travel.state.gov, which is
global but country-level with no sub-national geometry. Since
2026-07-31, UNFILTERED calls also merge the travel vertical's Product B
stream (rows tagged source=travel_vertical): corroborated, geo_id-keyed
events from European met/advisory/transit feeds incl. strikes — see
list_disruption_events for the richer filtered surface. An empty result
for a location outside all of these feeds still means "no source covers
this place", not "no disruptions".

Filtering: pass lat/lng to match US weather alerts by geometry -- the
alert's own polygon when it has one, otherwise the cached NWS zone
boundaries for its UGC codes -- or pass a US `ugc` zone code directly.
When lat/lng are set, the reply may also include rows with:
  - `source=nws_observation` Surface Visibility (nearest NWS station meters/miles, NOT landmark webcam)
  - `source=buoy_observation` Wave/wind from nearest NDBC buoy (height ft/m, period, wind kts) NEW v2
  - `source=forecast_observation` Hourly forecast next 6h with freeze/heat guidance NEW v2
  - `source=road_closure` Caltrans SR-1/Big Sur closures NEW v2
  - `source=aqi_observation` EPA AirNow AQI + outdoor seating advice NEW v2
  - `source=transit_disruption` BART/511 strike/delay NEW v2
  - `source=camera_vision` fresh ingest-side VLM row, else explicit `camera_observation` forecast fallback
  - `source=quake_observation` USGS earthquake M/dist NEW v2
  - `source=insurance_observation` NatCat risk synthesis NEW v2
  - `source=legal_observation` Federal Register recent rules NEW v2
  - `source=threat_observation` NVD CVE CVSS NEW v2
  - `source=vendor_observation` Supply chain / vendor risk NEW v2
Country-level advisories carry no geometry, so a lat/lng filter excludes
them; omit all filters to get every active alert including advisories.
Each CAP row carries severity/urgency/event/headline plus honest `freshness`
(alert_fresh|alert_stale) and `join_eligible` labels -- alerts inform,
they are never silently dropped. An empty CAP list is not all-clear.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No
`lng`	No
`ugc`	No
`limit`	No
`query`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context: live poller, partial and US-only feed coverage, country-level advisory limits, empty-result semantics, and `freshness`/`join_eligible` labels. There is no contradiction with annotations.

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?

Purpose and key caveats are front-loaded in the first paragraphs, and later source bullets are verbose but mostly justified by the data-coverage complexity. The length is high but each section contributes to avoiding misinterpretation of results.

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?

Covers source coverage, filtering behavior, country-level caveats, empty-result meaning, and honesty labels, while the output schema handles return-shape details. The only material omission is the meaning of `limit` and `query`, so it is nearly complete rather than fully complete.

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?

The description richly explains lat/lng and ugc semantics, adding real meaning beyond the bare schema titles. However, `limit` and `query` are never mentioned, and with 0% schema description coverage the description is the only documentation for them. This compensation is incomplete.

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?

Opens with 'active disruption alerts (weather, safety, travel advisories) for a region', clearly stating a specific verb, resource, and scope. It also differentiates itself from the sibling `list_disruption_events` by describing this as the unfiltered surface and pointing to that tool for richer filtering.

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?

Explicitly details when to use lat/lng versus `ugc`, and says to omit all filters to get every active alert including advisories. It names `list_disruption_events` as the richer filtered alternative, so an agent has concrete selection guidance.

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

All SeaWeb tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?