weather
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUHE_WEATHER_API_KEY | Yes | 你的API_KEY |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_weatherB | 查询中国城市的实时天气信息 |
| get_weather_detailsB | 获取城市的详细天气信息，包括未来几天预报 |
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
query_weather focuses on current real-time conditions while get_weather_details offers more comprehensive information with forecast data. There is some overlap because both retrieve weather, but the descriptions provide enough distinction.
Both names use a verb_noun pattern and are readable, but the mix of 'query' and 'get' is a slight inconsistency in retrieval verb choice.
Two tools is a thin surface for a weather server, but it still covers the two core needs: current conditions and forecasts. This is borderline rather than clearly excessive or inadequate.
Real-time weather and multi-day forecast cover the most common weather information needs for Chinese cities. Missing features like alerts or historical data are minor gaps rather than causes of failure.