Juhe Weather MCP Server
OfficialServer 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 |
|---|---|
| query_weatherC | 根据城市、地区、区县名称查询当地实时天气预报情况 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'query_weather' has a clear and distinct purpose of querying real-time weather forecasts based on location names.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query_weather' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a weather server's apparent scope, which typically involves forecasts, historical data, alerts, or multiple query types. This minimal set feels thin and limits functionality for agents.
The tool surface is severely incomplete for a weather domain. It only provides real-time queries, with obvious gaps like no support for forecasts (e.g., hourly, daily), historical data, weather alerts, or location-based searches beyond basic queries.