Weather MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELLER_WALLET | Yes | The Solana devnet public address that will receive payments |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherD | Call self as a function. |
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, as there are no other tools to confuse it with. The single tool's purpose is clearly defined as retrieving weather information.
Since there is only one tool, it inherently exhibits perfect naming consistency with itself. The tool name 'get_weather' follows a clear verb_noun pattern, which would be consistent if more tools existed.
A single tool for a weather server is too few for the apparent scope, as weather-related operations typically involve more functionality (e.g., forecasts, alerts, historical data). This minimal set feels thin and incomplete for the domain.
The tool surface is severely incomplete for a weather domain, offering only basic current weather retrieval. There are significant gaps, such as lack of forecast data, location-based searches, or historical weather information, which will likely cause agent failures in broader tasks.