my-weather-server-0706
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
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 |
|---|---|
| get_weatherA | 通过 my-weather-server-0706 获取指定城市的当前真实天气 |
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
Only one tool exists, so there is no possibility of confusing it with another. The purpose is clearly scoped to fetching current weather.
The single tool name follows a clear verb_noun pattern (get_weather), and there are no other tools to deviate from this convention.
With just one tool, the server feels thin for a general 'weather' service, as it only covers a single operation. However, it is a borderline case, not extreme.
The tool provides current weather, but obvious gaps like forecasts or historical data are missing, making the surface incomplete for a full weather server. Still, the core get-weather operation is present.