NWS Weather Alerts

get_alerts

Get active NWS weather alerts for a US state.

Returns current weather alerts including watches, warnings, and advisories
issued by the National Weather Service.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY').
    severity: Filter by severity level: 'Extreme', 'Severe', 'Moderate', or 'Minor'.
    event: Filter by event type (e.g. 'Tornado Warning', 'Flash Flood Watch').
    limit: Maximum number of alerts to return (default 25, max 500).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`event`	No
`limit`	No
`state`	Yes
`severity`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It explicitly states that results are 'current weather alerts including watches, warnings, and advisories' and mentions the active-alert scope. It also explains filtering by severity and event, providing useful behavioral context beyond a simple read operation.

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?

The description is succinct and well-structured. It front-loads the purpose in the first line, adds a brief output summary, and then presents a compact, dense Args block. No redundant or ambiguous wording.

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 that an output schema exists (indicated in context), the description need not explain return values. It thoroughly covers parameter semantics, default behavior, and the scope of results. The description is complete enough for an agent to select and use the tool correctly without additional information.

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?

Schema description coverage is 0%, so the Args section is crucial. It provides concrete examples for state ('CA', 'TX', 'NY'), exact allowed severity values, example event types, and the default/max limit. This goes far beyond the bare schema and gives agents everything needed to construct valid calls.

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?

Description opens with 'Get active NWS weather alerts for a US state,' using a specific verb and resource with clear scope. This distinctly separates it from sibling tools like get_alert_detail (single alert) and get_forecast (weather forecasts).

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 clearly implies when to use this tool: for retrieving active state-level alerts. It does not explicitly name alternatives or state when not to use, but since sibling tools serve different purposes, the usage context is clear. Could be improved by adding an explicit exclusion note.

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

All NWS Weather Alerts tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: get_alerts retrieves alerts by state, get_alert_detail provides details for a specific alert ID, and get_forecast returns weather forecasts by location. The descriptions clearly differentiate their functions, eliminating any potential for misselection.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'get_' prefix (get_alerts, get_alert_detail, get_forecast). This predictable naming convention makes the tool set easy to understand and navigate without any deviations in style.

Tool Count4/5

Three tools is reasonable for a weather alerts server, covering core functions: listing alerts, getting alert details, and retrieving forecasts. It's slightly minimal but well-scoped; adding tools like historical data or radar might enhance it, but the current count is appropriate for basic operations.

Completeness4/5

The tool set covers essential weather alert workflows: fetching alerts, accessing details, and obtaining forecasts. Minor gaps exist, such as no tools for historical alerts or broader geographic queries beyond states, but agents can work around these with the provided tools for most common use cases.

Resources

Need Help?