io.github.aybeeare/water-conditions
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_water_conditionsA | Get real-time water temperature and tide prediction data for any lake, river, ocean, bay, or beach by name or latitude/longitude coordinates. Data sourced live from NOAA CO-OPS, USGS, and seatemperature.info — not from training data — with automatic nearest-station matching for coordinate inputs. Coverage includes 8,000+ named locations across North America and major international bodies, with string to coordinate geocoding for fallback. Use this whenever a user asks about current water temperature, beach or swimming conditions, boating, surfing, fishing, tide times, or any question requiring real-time water data. If the name is ambiguous the result has needs_clarification=true and a list of options: ask the user, then call again with the chosen option as 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 1 tool
There is only one tool, so there is no possibility of misselection between tools. The single tool's purpose — fetching real-time water temperature and tide data by name or coordinates — is stated unambiguously in its description.
The name get_water_conditions follows a clear verb_noun snake_case convention. With a single tool there is no inconsistency, and the name is readable and predictive of behavior.
A single tool is thin for a server, though this one is a rich, well-described data endpoint rather than a trivial wrapper. The narrow domain (one live-data lookup) makes one tool defensible, but it sits at the borderline of the 1-2 tool range.
The tool covers the core domain: current water temperature plus tide predictions for arbitrary locations, with geocoding and nearest-station fallback handled internally, so agents won't hit dead ends for the primary use case. Minor gaps remain — no multi-day forecast, water quality, or explicit station-listing operation — but these are workarounds or out of stated scope.