weather
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_alertsB | Get weather alerts for a US state. |
| get_forecastC | Get weather forecast for a location. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weather_briefing | Ask for a concise severe weather briefing for a US state. |
| trip_packing_advice | Ask for packing advice based on the forecast for a location. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_states | List of valid two-letter US state codes accepted by the alerts resource/tool. |
| alerts_ca | Weather alerts for CA. |
| alerts_ny | Weather alerts for NY. |
| alerts_tx | Weather alerts for TX. |
| alerts_fl | Weather alerts for FL. |
TDQS
Scored across 2 tools
The two tools are clearly distinct: get_alerts handles weather alerts for a US state, while get_forecast provides forecasts for specific coordinates. There is no ambiguity about which tool to use for which purpose.
Both tools follow a consistent verb_noun pattern (get_alerts, get_forecast) using the same verb 'get' and snake_case convention. The naming is perfectly consistent.
With only 2 tools for a weather domain, the surface feels very thin. Weather servers typically need additional operations like current conditions, radar, air quality, or reverse geocoding to be genuinely useful.
The domain of weather covers more than alerts and forecasts. There are notable gaps: no current conditions, no historical data, no multi-day/hourly breakdown details, and no reverse geocoding for the coordinate-based forecast.