Weather MCP
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 |
|---|---|
| get-alertsC | Get weather alerts for a state |
| get-forecastC | Get weather forecast for a 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 2 tools
The two tools have clearly distinct purposes: one retrieves weather alerts for states, while the other provides forecasts for locations. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the need.
Both tools follow a consistent verb_noun pattern with 'get-' prefix and hyphenated names (get-alerts, get-forecast). This uniformity makes the tool set predictable and easy to understand.
With only two tools, the server feels under-scoped for a weather domain. Key operations like getting current conditions, historical data, or radar imagery are missing, making the set too thin for comprehensive weather-related tasks.
The tool set is severely incomplete for a weather server. It lacks basic operations such as current weather, historical data, or severe weather details, creating significant gaps that will hinder agents in performing common weather-related workflows.