io.github.wcnm8888/mcp1-weather-query
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherA | Resolve a city or postal-code-like location and return read-only, model-based current conditions. This Tool does not provide forecasts, alerts, advice, or arbitrary URL content. Always inspect resolved_location because place names can be ambiguous. |
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 zero ambiguity in tool selection. The tool's purpose is clearly distinct by being the sole option.
The single tool name 'get_current_weather' follows the standard verb_noun pattern, which is clear and predictable.
One tool is minimal, but the server's scope is explicitly limited to current conditions, making the count reasonable if slightly thin.
For the stated purpose of returning current weather conditions, the tool fully covers the domain; forecasts and alerts are intentionally excluded.