nws-mcp-server
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_alertsA | Get weather alerts for a state |
| get-forecastC | Get weather forcast for a location |
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 2 tools
The two tools serve clearly distinct purposes: one for weather alerts and one for forecasts. There is no overlap in functionality.
Both tools follow a verb_noun pattern, but one uses underscores (get_alerts) while the other uses a hyphen (get-forecast). This inconsistency could confuse an agent expecting uniform naming.
With only two tools, the server feels too thin for a comprehensive weather service. While it covers alerts and forecasts, it lacks other common NWS operations like current conditions.
The tool set provides only alerts and forecasts, missing significant NWS operations such as current observations, radar, or marine forecasts. This creates notable dead ends for agents.