Skip to main content
Glama

Live NWS forecast and alerts for a location (U.S.)

get_nws_forecast_and_alerts
Read-onlyIdempotent

Use for trip-day weather and heat or cold risk at a trailhead, campsite, park entrance or jobsite in the U.S. Returns active National Weather Service alerts (e.g. Heat Advisory, Excessive Heat Warning, Winter Storm Warning, Flash Flood Warning, Red Flag Warning) and the next forecast periods for a latitude/longitude, straight from api.weather.gov, with the forecast page link. U.S. and territories only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_nws_forecast_and_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsNoNumber of 12-hour forecast periods to return
latitudeYesDecimal degrees, e.g. 36.1069
longitudeYesDecimal degrees, e.g. -112.1129

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, open-world lookup, so the description's main added value is disclosing the live upstream source (api.weather.gov) and the kinds of alerts returned. It does not cover rate limits, failure behavior when no alerts are active, or freshness guarantees, which leaves some behavioral uncertainty.

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?

Two tight sentences, with the use case and scope front-loaded before the return details and geographic constraint. Every clause contributes either purpose, output content, source, or scope.

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 simple two-required-parameter lookup with no output schema, the description explains the source, scope, and return content well enough to call it correctly. It could say more about the shape of the returned forecast periods or how alerts are represented, but the essential context is present.

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 latitude, longitude, and the periods parameter are already fully documented in the schema. The description adds no extra meaning about the periods parameter or coordinate conventions beyond what the schema provides, making the baseline 3 appropriate.

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?

The description gives a specific verb-and-resource pairing: return active NWS alerts and forecast periods for a latitude/longitude. It clearly frames the tool around trip-day weather and heat/cold risk, which separates it in practice from the safety-guidance and park-condition siblings, though it does not name an alternative explicitly.

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?

It states when to use it (trip-day weather, heat or cold risk at a trailhead, campsite, park entrance, or jobsite) and gives a hard geographic exclusion (U.S. and territories only). It does not point to alternative tools or explain what to do outside the U.S., so it stops short of full routing guidance.

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