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 AI-generated summaries. If not set, the server returns structured JSON instead of an AI 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
With only a single tool, there is no possibility of ambiguity or confusion between different functions.
The single tool name 'get_weather' follows a clear, conventional verb_noun pattern, consistent with common MCP naming practices.
One tool is at the lower boundary of what is reasonable for a weather server; it feels slightly thin but not entirely inadequate given the combined current/forecast functionality.
The tool covers basic conditions and forecast but lacks common weather-related operations such as alerts, historical data, or location management, leaving notable gaps for a full-featured weather service.