HeFeng 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 |
|---|---|
| get-weatherB | 获取中国国内的天气预报 |
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 confusion or overlap between tools. The tool's purpose is clearly defined as fetching weather forecasts for China, leaving no ambiguity for an agent to misselect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get-weather' follows a clear verb-noun pattern, and there are no other tools to deviate from this pattern.
A single tool is too few for a weather server's apparent scope, which typically involves multiple operations like current conditions, forecasts, alerts, or location-based queries. This minimal set limits functionality and feels thin for the domain.
The tool surface is severely incomplete for a weather domain. It only provides forecasts for China, missing essential operations such as current weather, historical data, alerts, or support for other regions, which will likely cause agent failures in broader tasks.