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
get_alerts and get_forecast have clearly distinct purposes: one returns alerts for a US state, the other returns a forecast for coordinates. There is no ambiguity between the two.
Both tools follow the same get_ noun pattern, making the naming predictable and consistent. The singular/plural difference (forecast vs. alerts) is semantically appropriate.
With only two tools, the server feels thin for a weather domain, but it is still within a borderline range. Each tool provides a distinct core weather function, so the count is not unreasonable.
The weather domain typically includes current conditions, forecasts, and alerts. This server lacks current weather data and only handles forecasts and alerts, which is a significant gap for general weather use.