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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Get the current weather and 1-7 day forecast for a specific location. |
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 confusion or overlap. Every tool (the only tool) has a clearly distinct purpose.
The single tool name 'get_weather' follows a consistent verb_noun pattern, which is a standard and clear convention. There are no other tools to create inconsistency.
The server has exactly one tool, which feels too thin for the apparent scope of a weather service. While the tool covers current and forecast data, a typical weather server might offer additional operations like alerts or historical data.
The single tool covers the core weather use case of current conditions and 1-7 day forecast. Minor gaps exist—such as weather alerts, historical data, or multi-location retrieval—but they are not essential to the primary purpose.