mcp-weather-tool
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-weatherC | Tool to fetch the weather of a city |
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 ambiguity or overlap. The purpose is clearly defined as fetching weather for a city.
The single tool name 'fetch-weather' follows a consistent verb-noun pattern, which is predictable and clear.
A single tool is too few for a weather service, which typically requires multiple operations such as current conditions, forecasts, and historical data. The apparent scope of a weather tool is broader than what one fetch operation can cover.
The tool provides basic weather fetching but lacks common weather operations like forecasts or historical data. This leaves noticeable gaps in the tool surface for a weather domain.