Skip to main content
Glama

Check active US weather alerts for a state or point

weather_alerts
Read-only

Active US National Weather Service alerts for a state or a point: event, severity, urgency, area, onset, end of the event (ends), expiry of this message (expires), headline and instruction (cut to 400 characters). Attribution: National Weather Service, public domain. Takes about 15 s; allow a 30 s timeout. Related tools on this server, for a different need: weather when you need Weather for a place or a coordinate: current conditions. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, with lon, instead of state
lonNoLongitude
stateNoTwo-letter US state, e.g. CA

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
alertsNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: discloses the data source and public-domain attribution, the truncation of instruction to 400 characters, the distinction between 'ends' (event end) and 'expires' (message expiry), latency and timeout budget, and the pricing model including that failed calls are not charged. That is exactly the extra context annotations cannot carry.

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?

Front-loads purpose, then fields, then attribution, latency, alternative tool, and price — every element is useful. It is dense as a single paragraph and the pricing sentence is long, but no sentence is filler.

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?

For a zero-required-param lookup with an output schema, the description covers source authority, coverage (US), latency/timeout, billing, and truncation behavior. An agent has everything needed to call it, budget for it, and interpret the response.

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 the lat/lon/state semantics are already documented, including 'with lon, instead of state'. The description reinforces the either/or ('a state or a point') but adds no format, default, or precedence detail beyond the schema.

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?

States a specific verb and resource — 'Active US National Weather Service alerts' — plus the two input modes (state or point) and the payload fields. It also explicitly separates itself from the sibling 'weather' tool by noting that one covers current conditions, so an agent can route without opening either schema.

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?

Names the alternative ('weather ... current conditions') and the need that selects it, which is real routing guidance rather than none. It also gives an operational guideline — ~15 s runtime, allow a 30 s timeout — but does not say when alerts are inappropriate or what to do with no active alerts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources