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
The two tools have clearly distinct purposes: one for weather alerts by state, another for forecast by coordinates. No overlap in functionality.
Both tools follow a consistent verb_noun pattern (get_alerts, get_forecast), making the naming predictable and easy to understand.
With only two tools, the server feels minimal for a weather domain. While it covers two core functions, 2 tools is on the lower end of reasonable scope.
The server provides alerts and forecast but lacks current conditions, radar, or marine data, leaving notable gaps for a typical weather information service.