nws-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_forecastA | Multi-day US weather forecast from the National Weather Service. Returns named periods (e.g. "Tonight", "Thursday") with temperature, wind, and a short description. |
| get_hourly_forecastB | Hour-by-hour US weather forecast from the National Weather Service, with temperature, precipitation probability, and wind for each hour. |
| get_active_alertsA | Active National Weather Service alerts, watches, and warnings — for a specific point, or for an entire state with the "state" argument. |
| get_current_conditionsA | Latest observation from the National Weather Service station nearest a US location: temperature, wind, humidity, pressure, visibility, and how old the reading is. |
| get_grid_infoA | The National Weather Service grid metadata for a US location: forecast office, grid cell, radar station, and forecast/county zones. Useful for understanding which office issues a forecast and for building further NWS API calls. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct data product: multi-day forecast, hourly forecast, active alerts, latest observation, and grid metadata. The only near-neighbor pair (get_forecast vs get_hourly_forecast) is unambiguously separated by name and by the explicit 'multi-day periods' vs 'hour-by-hour' descriptions.
All five tools follow a strict snake_case get_<resource> pattern with no verb or casing deviations. The naming reads predictably and maps cleanly onto the returned resource.
Five tools is well within the well-scoped range, and each tool maps to a genuinely different NWS endpoint with no redundant overlap. Nothing feels padded or missing at the count level.
The core weather surface (daily forecast, hourly forecast, current conditions, alerts, grid metadata) is fully covered with no dead ends for typical use. Minor gaps exist around historical observations, station search, and narrative forecast-discussion text products, which agents would have to work around.