Weather API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QWEATHER_API_KEY | No | Your QWeather API key for authentication | |
| QWEATHER_API_URL | No | The QWeather API base URL | https://devapi.qweather.com/v7 |
| QWEATHER_GEO_API_URL | No | The QWeather Geo API base URL | https://geoapi.qweather.com/v2 |
| WEATHER_DEFAULT_UNITS | No | Default temperature units (metric or imperial) | metric |
| WEATHER_FORECAST_DAYS | No | Default number of days for forecast (max 30) | 3 |
| WEATHER_INCLUDE_DETAILS | No | Whether to include detailed information in responses | true |
| WEATHER_DEFAULT_LANGUAGE | No | Default language code for responses | en |
| WEATHER_DEFAULT_LOCATION | No | Default location code or coordinates |
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 |
|---|---|
| getWeatherC | Get current weather information for a location. Returns weather data including temperature, humidity, and conditions. |
| getWeatherForecastB | Get weather forecast for a location. Returns weather forecast for the next few days. |
| getHourlyWeatherC | Get hourly weather forecast for a location. Returns weather data hour by hour for the next 24 hours. |
| lookupCityB | Look up city information by name, ID, or coordinates. Returns city ID that can be used with other weather tools. |
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 4 tools
The tools have overlapping purposes that could cause confusion. getWeather, getHourlyWeather, and getWeatherForecast all retrieve weather data for a location, differing only in time granularity. While descriptions clarify the distinctions, an agent might misselect between them without careful reading. The lookupCity tool is clearly distinct, but the three weather retrieval tools create ambiguity.
Naming is mostly consistent with a verb_noun pattern, though there are minor deviations. getWeather, getHourlyWeather, and getWeatherForecast follow a clear get_<type>Weather pattern, while lookupCity uses a different verb (lookup vs. get). All use camelCase consistently, making them readable despite the verb variation.
Four tools is well-scoped for a weather API server. Each tool earns its place: current weather, hourly forecast, multi-day forecast, and city lookup provide complete coverage without bloat. This count aligns with typical server scopes (3-15 tools) and avoids being too thin or heavy.
The tool set covers core weather API operations effectively, with minor gaps. It includes current conditions, short-term and long-term forecasts, and location lookup, enabling agents to handle most weather queries. However, there are no tools for historical weather data or alerts, which could be useful extensions for the domain.