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 |
|---|---|
| getWeatherC | Get current weather for 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 possibility of ambiguity or overlap between tools. The tool 'getWeather' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb_noun pattern with 'getWeather', and since there is only one tool, there are no deviations or mixed conventions to evaluate. The naming is straightforward and predictable.
A single tool for a weather server is too few for the apparent scope, as it only provides current weather retrieval. This lacks essential operations like forecasts, historical data, or location-based queries, making it feel thin and incomplete for typical weather-related tasks.
The tool surface is severely incomplete for a weather domain. It only covers current weather retrieval, with significant gaps such as missing forecast data, historical weather information, or multi-location queries. This will likely cause agent failures when broader weather-related needs arise.