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_alertsA | Get weather alerts for a US state. Args: state: Two-letter US state code (e.g. CA, NY) |
| get_forecastC | Get weather forecast for a location. Args: latitude: Latitude of the location longitude: Longitude of the 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 retrieves alerts by state, the other provides forecasts by coordinates. There is no functional overlap or ambiguity.
Both tools follow a consistent 'get_noun' pattern with snake_case, making the names predictable and easy to understand.
With only two tools, the server is minimal but still covers two core weather functionalities. It feels slightly thin but is acceptable for a focused server.
The server covers alerts and forecasts but lacks current conditions, historical data, or other common weather endpoints. Notable gaps exist, but the core stated purpose is partially met.