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_alertsA | Get weather alerts for a US state. Args: state: Two-letter US state code (e.g. CA, NY) |
| get_forecastC | Get weather forecast for a location. Args: latitude: Latitude of the location longitude: Longitude of the 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 are clearly distinct: get_alerts retrieves weather warnings for a state, while get_forecast retrieves forecast data by coordinates. There is no overlap in their inputs or outcomes.
Both tools follow the same 'get_noun' pattern, with get_alerts and get_forecast. The naming is predictable and consistent.
With only two tools, the server is minimal and borderline scoped. While this could be fine for a specialized alerts/forecast service, it feels thin for a general weather service and does not reach the 3-15 tool sweet spot.
A weather service would typically include current conditions, hourly/daily details, or location-based lookup beyond forecast and alerts. The absence of these leaves significant gaps for users expecting general weather coverage.