SHEARLINE
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_active_warningsA | Active NWS severe-weather warning polygons near a CONUS point. |
| get_spc_outlookA | SPC convective outlook at a CONUS point for day 1, 2, or 3. Returns the categorical risk (TSTM/MRGL/SLGT/ENH/MDT/HIGH) plus hazard probabilities (tornado/hail/wind for days 1-2; total severe for day 3) and significant-severe flags, with an interpretation calibrated to the category. |
| get_point_environmentA | RAP-analysis severe-weather environment at a CONUS point. |
| get_environment_trendA | RAP forecast-environment trend at a CONUS point (the anticipatory view). |
| get_mrms_severeA | MRMS radar-derived severe weather products near a CONUS point. |
| get_lightningA | GOES GLM total-lightning activity near a CONUS point in the recent window. |
| get_storm_reportsA | Local Storm Reports (spotter/official reports) near a CONUS point. |
| get_historical_storm_reportsA | Local Storm Reports near a CONUS point on a specific PAST date. |
| get_threat_briefA | Composite severe-weather threat brief for a CONUS point. |
| get_radar_snapshotA | Latest NEXRAD Level 2 volume metadata from the nearest WSR-88D radar. |
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 10 tools
Each tool targets a clearly different severe-weather data source or time horizon: warnings, outlook, analyzed environment, forecast trend, MRMS products, lightning, current reports, historical reports, radar metadata, and a composite brief. Even the two radar-related tools are cleanly separated by purpose, and get_point_environment/get_environment_trend are explicitly distinguished as now vs forecast.
All ten tools follow a consistent get_<descriptive_noun> pattern that reflects both action and resource. The names are uniformly snake_case with no mixed conventions or vague verbs.
Ten tools is well within the ideal range and each one corresponds to a distinct severe-weather data product needed for situational awareness. The count is neither bloated nor too thin for the server's stated domain.
The surface covers the full severe-weather assessment workflow: current warnings, forecast outlooks, current and trended environment parameters, observed radar/lightning, recent and historical storm reports, and a synthesizing brief. There are no obvious dead ends or missing operations for a point-based CONUS severe-weather tool.