Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEATHER_API_KEY | No | Your OpenWeatherMap API key. Get a free API key from https://openweathermap.org/api. If no API key is provided, the server will use mock data for demonstration purposes. |
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 |
|---|---|
| get_current_weatherC | Get current weather conditions for a specific location |
| get_weather_forecastC | Get weather forecast for a specific location for multiple days |
| search_locationsC | Search for location names matching a query string |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_weather | Analyze weather patterns and provide insights about current conditions |
| compare_locations | Compare weather conditions between multiple locations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Weather | Current weather data for any location |
| Weather Forecast | Weather forecast data for any location |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_current_weather retrieves current conditions, get_weather_forecast provides future predictions, and search_locations handles location queries. An agent can easily differentiate between these three functions.
All tools follow a consistent verb_noun naming pattern (get_current_weather, get_weather_forecast, search_locations) with clear, descriptive names. There are no deviations in style or convention across the toolset.
Three tools is reasonable for a weather server, covering core functions like current conditions, forecasts, and location search. However, it feels slightly thin as it lacks tools for historical weather data or alerts, which are common in weather APIs.
The toolset covers essential weather operations: retrieving current data, forecasts, and location lookup. A minor gap exists in not including historical weather data or severe weather alerts, but agents can still perform most common weather-related tasks effectively.