Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | API key for Groq to enable AI-generated summaries. Optional; if not set, the server returns structured JSON instead of a natural language summary. |
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_weatherA | Get current conditions and a weather forecast for a place. Args: location: A city, region, or country name, such as "London" or "Tokyo". forecast_days: Number of forecast days to return, from 1 through 7. |
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 single tool has a clear, unique purpose.
The tool name follows the standard verb_noun pattern (get_weather), which is clear and predictable. With only one tool, consistency is trivially maintained.
A single tool feels thin for a weather-focused server, even though get_weather covers both current conditions and forecasts. The server is on the low end of acceptable scope.
The tool covers the core weather use cases: current conditions and multi-day forecasts. Obvious gaps like historical data or weather alerts exist, but the essential surface is present.