windext
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_spotA | Look a spot up by name in the windext spot database (community-built, with beach orientation and wind-direction knowledge), then fall back to geocoding. Always call this first. |
| spot_infoC | Full card of a known spot, or the spots known within a radius of a point. |
| submit_spotA | Add a spot to the open windext database, or correct an existing one. Only call after the user has confirmed the facts. Cards are stored with status "community" until a moderator verifies them; a correction to a verified spot is queued for review. Licence CC BY-SA, no personal data. |
| spot_forecastB | Hourly wind forecast from several weather models at once (AROME, ICON, ECMWF, GFS, UKMO, plus KNMI/DMI in Europe), compiled into one compact table with model consensus, spread, agreement, gust factor and shore relation, followed by a diagnosis of why the wind is gusty or steady. Pass spot_id when known. |
| ride_windowsB | Contiguous daytime windows where the model-consensus wind sits inside the rider's range, excluding offshore wind and the spot's forbidden sectors unless allowed. |
| tidesA | High and low water times and heights (vs mean sea level) for a coastal spot, from the Open-Meteo marine model. Approximate (+/- 20 min), free, worldwide; not for navigation. Empty for lakes. |
| list_modelsB | Which weather models windext reads by default at a location, and their resolution/coverage notes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| session_check | Is it worth going riding at a spot? Reasoned like an experienced rider. |
| spot_compare | Which of two spots to choose on a given day. |
| weekend_planner | Best session of the coming weekend among the spots near a place. |
| gear_advice | Gear size for a rider at a spot on a day. |
| explain_gusts | Plain-language explanation of the gustiness at a spot on a given day. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct capability (search, spot details, submission, forecast, riding windows, tides, model metadata), and the descriptions give clear sequencing cues like 'always call this first.' The main soft spot is find_spot vs spot_info, which both surface spot data, but the descriptions adequately separate search-by-name from a full card/radius lookup.
Names are readable snake_case but mix conventions: verb_noun forms (find_spot, submit_spot, list_models) sit alongside noun-noun forms (spot_info, spot_forecast) and bare nouns (tides, ride_windows). A single consistent pattern like get_spot, get_forecast would be cleaner, though the domain theme keeps it understandable.
Seven tools is well-scoped for a wind-forecast/spot database server. Each tool covers a distinct piece of the domain (discovery, detail, contribution, forecast, derived windows, tides, model info) with no filler.
The core lifecycle is covered: find spots, view details, submit/correct spots, get forecasts, derive ride windows, check tides, and inspect models. Minor gaps exist (no saved/favorite spots, user preferences for rider range, or alerts), but agents can work around these.