Weather 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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_alertsB | Get weather alerts for a state |
| get_forecastB | Get weather forecast for a location |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weather-briefing | Generate a comprehensive weather briefing for a US state, including active alerts and forecast |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve completely distinct purposes: one for weather alerts and one for forecasts, making misselection unlikely.
Both tools follow the consistent verb_noun pattern using snake_case: get_alerts and get_forecast.
With only 2 tools, the server feels thin; weather services typically benefit from additional tools like current conditions or hourly forecasts.
The set covers alerts and forecasts but misses common weather operations such as current conditions, historical data, or location search.