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 | 获取指定城市的天气预报信息。支持1-16天的天气预报，包括温度、风力、舒适度、降雨降雪、紫外线指数、PM2.5等详细信息。 |
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's purpose is clearly defined as fetching weather forecasts for a specified city.
The single tool name 'get_weather' follows a clear verb_noun pattern. Since there are no other tools to compare, consistency is inherently perfect.
A single tool is too few for a weather server, as it lacks operations like searching locations, getting historical data, or setting preferences. This minimal set limits functionality and may cause agent failures in broader weather-related tasks.
The server is severely incomplete for a weather domain. It only provides forecast retrieval, missing essential operations such as current conditions, alerts, location search, or multi-city queries, which are standard in weather APIs.