Basic 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-weatherC | Tool to fetch weather information |
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 'fetch-weather' has a clear and distinct purpose, making it impossible for an agent to misselect among non-existent alternatives.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch-weather' follows a verb_noun pattern, and with no other tools to compare against, there are no deviations or inconsistencies in naming conventions.
A single tool for a weather server is too few for the apparent scope, as weather-related operations typically involve more than just fetching data (e.g., forecasts, historical data, or location-based queries). This minimal set feels thin and limits functionality, indicating a mismatch with the domain's needs.
The tool surface is severely incomplete for a weather domain. While 'fetch-weather' provides basic retrieval, there are obvious gaps such as lacking forecast tools, historical data access, or location-specific queries. This will likely cause agent failures when more comprehensive weather information is needed.