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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_alertsD | – |
| get_forecastD | – |
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 2 tools
The two tools, get_alerts and get_forecast, have clearly distinct purposes. An agent can easily differentiate between retrieving weather alerts and obtaining a forecast, with no overlap in functionality.
Both tools follow a consistent verb_noun pattern using snake_case (get_alerts, get_forecast), ensuring predictable and uniform naming.
With only two tools, the server's scope feels somewhat thin for a weather-related service. While it covers the basics, a typical weather server would benefit from additional tools like current conditions or location search.
The tool set covers alerts and forecasts, but lacks common operations such as current conditions or historical data. This represents a notable gap that may hinder comprehensive weather queries.