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-alertsC | Get weather alerts for a US state |
| get-forecastB | Get weather forecast for a location in the US |
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 target clearly different resources: alerts (hazard notifications) versus forecast (predicted conditions). There is no plausible scenario where an agent would confuse them.
Both tools follow an identical get-<resource> pattern in kebab-case. The convention is predictable and would extend cleanly if more tools were added.
Two tools is on the thin side for a weather server; there is no tool for current observations, hourly data, or location lookup. Each tool earns its place, but the surface feels minimal rather than well-scoped.
Core weather use cases (alerts and forecast) are covered, but notable operations are missing: current conditions, hourly forecasts, and any way to resolve a place name to coordinates. Agents can work around this with external knowledge but will hit dead ends for common requests.