Context 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_forecastC | |
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 targets state-level weather alerts, while get_forecast targets point-based forecast. No overlap in purpose or arguments.
Both tools follow a consistent get_verb_noun pattern (get_alerts, get_forecast), which is predictable and clear.
With only 2 tools, the server feels minimal. While it serves a focused purpose, a typical weather API would offer more operations, making the count borderline.
The server covers alerts and forecast, but lacks current conditions or radar data. The gaps are minor given the server's 'context' focus.