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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_alertsB | Get weather alerts for a US state. |
| get_forecastC | Get weather forecast 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
get_alerts and get_forecast have clearly distinct purposes: one retrieves alerts by state, the other retrieves forecasts by coordinates. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_alerts, get_forecast). The naming is predictable and readable.
Two tools is thin for a general weather server. Many common operations (e.g., current conditions, historical data) are absent, making the set feel minimal.
The server covers alerts and forecasts but lacks current conditions, hourly forecasts, or other standard weather data. This is a notable gap for the stated purpose.