Skip to main content
Glama

Get active weather alerts

get_active_alerts
Read-only

Retrieves active National Weather Service alerts, watches, and warnings for a specific US location or an entire state, returning markdown or JSON.

Instructions

Active National Weather Service alerts, watches, and warnings — for a specific point, or for an entire state with the "state" argument.

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

Input Schema

NameRequiredDescriptionDefault
placeNoUS place name to look up, as "City, ST" (e.g. "Tucson, AZ") or a full street address. Provide either this or latitude+longitude, not both.
stateNoTwo-letter US state or territory code (e.g. "AZ") to get every active alert in that state. Use instead of place/latitude/longitude.
latitudeNoLatitude in decimal degrees. Must be paired with longitude.
longitudeNoLongitude in decimal degrees. Must be paired with latitude.
response_formatNomarkdown for a compact human/LLM-readable summary, json for the structured object.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add context. It contributes that results come from the National Weather Service (implying US-only coverage) and that only *active* alerts are returned, but says nothing about empty results when no alerts are in effect, rate limits, or the shape of the payload.

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?

A single front-loaded sentence with the resource named first and the two usage modes following. No filler, hedging, or redundant restatement of the title.

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?

For a read-only lookup with full schema coverage and no output schema, the description covers what the tool returns and how to scope it. The one remaining ambiguity is that zero parameters are required, so an agent cannot infer from either description or schema what an argument-less call would do.

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 every parameter is already documented in the schema, including the place/lat-long exclusivity and the response_format enum. The description only restates the "state" argument's behavior, adding no format or precedence detail beyond what the schema provides; baseline 3 applies.

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 resource (National Weather Service active alerts, watches, and warnings) and states the two retrieval modes: single point or whole state. It is clearly distinguishable in kind from the forecast/conditions siblings, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the choice between point-based and state-wide retrieval and ties the latter to the "state" argument, which is useful routing guidance. It gives no explicit when-to-use versus the forecast siblings, and no guidance on what happens if the tool is called with no location arguments at all (all five parameters are optional).

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