Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

nws_active_alerts

Read-only

Fetch real-time active weather alerts from the National Weather Service. Filter by state, event type, or severity to get current watches, warnings, and advisories.

Instructions

List CURRENTLY-ACTIVE National Weather Service alerts — watches, warnings, and advisories (keyless; api.weather.gov). The disaster/climate-readiness lane that pairs with the FEMA tools (declarations → public assistance → hazard mitigation → LIVE active weather): where severe-weather events are active NOW, ahead of the declarations/contracts that follow. Filters: state (2-letter code → server-side ?area=, e.g. 'CA'; omit for all US), event (case-insensitive substring, e.g. 'Flood', 'Wind'), severity (Extreme/Severe/Moderate/Minor/Unknown); limit/offset pagination. Each alert: { id, event, headline, severity, urgency, certainty, category, status, messageType, areaDesc, effective, onset, expires, ends, senderName, description, instruction, response }. HONESTY: this is REAL-TIME data (alerts active at request time — a live snapshot, NOT a historical archive; read effective/expires for each window, disclosed in _meta); every scalar is null-never-empty-string and dates are ISO strings; totalAvailable is the EXACT count of matched active alerts; a NO-active-alerts result is an HONEST EMPTY (returned:0), never an error; an outage/4xx/timeout THROWS and a non-FeatureCollection body ⇒ schema_drift. A descriptive User-Agent is sent per NWS policy (no key/token).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoFilter by event type — case-insensitive substring, e.g. 'Flood', 'Wind', 'Winter Storm'.
limitNoMax alerts returned (default 50, max 500).
stateNo2-letter US state/territory code to scope alerts (→ NWS ?area=), e.g. 'CA'. Omit for all active US alerts.
offsetNoZero-based page offset (default 0).
severityNoFilter by severity (exact): Extreme | Severe | Moderate | Minor | Unknown.
Behavior5/5

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

The description goes far beyond the annotations by disclosing that data is real-time, a live snapshot, not historical; that null values are never empty strings; that totalAvailable is exact; that empty results are not errors; that outages throw; and that schema drift is detected. It also confirms a descriptive User-Agent is sent. No contradictions 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?

The description is long but well-structured: it starts with the main purpose, then explains the lane context, lists filters, describes the alert object, and ends with behavioral notes. Every sentence adds value, though it could be slightly more condensed.

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

Completeness5/5

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

Given the tool's complexity (5 parameters, no output schema), the description is highly complete. It covers the tool's purpose, all filters, return object fields, behavioral nuances (null handling, error behavior), and usage context. It leaves no critical gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description still adds significant value by explaining each parameter in detail, such as 'case-insensitive substring' for event, '2-letter code → server-side ?area=' for state, and pagination defaults (limit 50, max 500). It provides context beyond the schema descriptions.

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?

The description clearly states 'List CURRENTLY-ACTIVE National Weather Service alerts' with specific verbs and resource. It distinguishes from sibling tools by noting it is the 'disaster/climate-readiness lane that pairs with the FEMA tools' and that it shows live alerts as opposed to historical data or other FEMA-related actions.

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 description explains each filter (state, event, severity, limit, offset) with usage details like 'omit for all US' and 'case-insensitive substring'. It provides context that the tool is for real-time alerts and pairs with FEMA tools, but does not explicitly state when not to use or list specific alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cliwant/mcp-sam-gov'

If you have feedback or need assistance with the MCP directory API, please join our Discord server