rudra-weather-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-alertsA | Get the active weather alerts for a US state |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The purpose is clearly defined as retrieving active weather alerts for a US state.
The single tool name 'get-alerts' follows a clear verb-noun pattern. With only one tool, naming is trivially consistent.
One tool is borderline; it feels thin for a server named 'weather-mcp', but it is appropriately focused for a single-purpose alerts service.
The server only provides alerts, leaving obvious gaps in weather data such as current conditions and forecasts. The surface is too limited for a weather-focused MCP.