Weather API 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherB | Get current weather for a place. Wind speed is returned in km/h. |
| get_forecastC | Get a daily weather forecast for 1–7 days for a 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_weather and get_forecast have clearly distinct purposes: current conditions versus daily forecast. An agent can easily choose the correct tool based on whether it needs present weather or a multi-day outlook.
Both tools follow a consistent get_<noun> pattern. The naming is predictable and directly reflects the returned data.
Two tools are thin for a weather API surface, though they cover the most common current-weather and forecast use cases. Additional tools for hourly forecasts, alerts, or location lookup would make the set feel more complete.
The core weather workflow—current conditions and 1–7 day forecasts—is covered without dead ends. Minor gaps remain around hourly forecasts, severe weather alerts, and location resolution/geocoding.