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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weather_currentC | Get current weather for a location |
| weather_forecastC | Get weather forecast (1-14 days) for a location |
| weather_searchC | Search for locations matching query |
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 3 tools
Each tool has a clearly distinct purpose: weather_current retrieves current conditions, weather_forecast provides future predictions, and weather_search finds locations. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'weather_' prefix pattern with descriptive suffixes (current, forecast, search). This uniform naming convention makes the tool set predictable and easy to understand.
With 3 tools, the server is well-scoped for a weather service, covering core needs: current conditions, forecasts, and location lookup. Each tool earns its place without being excessive or insufficient.
The tool set covers essential weather operations for a typical agent, including current data, forecasts, and location search. A minor gap might be historical weather data, but core workflows are well-supported without dead ends.