windscout-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_spotsA | Search for a wind spot by Windfinder slug or name. Returns spot info including coordinates. Call this first to get lat/lon and spotId for other tools. |
| get_live_measurementsA | Get current real-time wind measurements from a Windfinder weather station. Requires spotId from search_spots. |
| get_forecastA | Get hourly wind and weather forecast for up to 16 days. Uses Open-Meteo. Wind speed provided in kn, km/h, and m/s. |
| get_marine_forecastA | Get hourly wave and swell forecast for up to 7 days. Uses Open-Meteo Marine API. Includes wave height (m), period (s), and direction. |
| get_tidesA | Get high/low tide times and heights for a coastal Windfinder spot. Requires spotId from search_spots. Returns empty for inland spots. |
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 5 tools
Each tool targets a distinct aspect: general forecast, live measurements, marine forecast, tides, and spot search. There is no overlap in functionality, and the descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern with snake_case: get_forecast, get_live_measurements, get_marine_forecast, get_tides, and search_spots. The only minor deviation is search instead of get, but it is a different action (search vs retrieve) and still fits the pattern.
With 5 tools, the server is well-scoped for a wind and weather information service. Each tool provides essential functionality without unnecessary bloat or gaps.
The set covers key use cases: spot search, real-time wind, hourly forecast, marine forecast, and tides. A minor gap is the lack of historical data or detailed spot metadata beyond coordinates, but the core workflows are supported.