Skip to main content
Glama
Sign In
io.github.aybeeare/water-conditions

io.github.aybeeare/water-conditions

by aybeeare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Water Conditions

get_water_conditions
Read-onlyIdempotent

Retrieve real-time water temperature and tide predictions for lakes, rivers, oceans, bays, and beaches by name or coordinates, with nearest-station matching for accurate local conditions.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
latitudeNoLatitude in decimal degrees, for nearest-station lookup when no location name is available. Requires longitude.
locationNoWater body name as natural language. Examples: 'Lake Michigan', 'Revere Beach', 'Chesapeake Bay', 'Cape Cod', 'Galveston Island', 'Puget Sound', 'Florida Keys', 'Potomac River', 'Waikiki Beach'. Provide this OR latitude+longitude.
longitudeNoLongitude in decimal degrees, for nearest-station lookup when no location name is available. Requires latitude.

Output Schema

NameRequiredDescriptionDefault
noteNoWhy there is no temperature, when temp_f is absent
tidesNoToday's high/low tide predictions; empty for non-tidal water
sourceNoWhere the temperature came from
temp_cNoWater temperature, °C
temp_fNoWater temperature, °F. Absent when no current reading exists (see note)
messageNoWhat to do next when needs_clarification is true
optionsNoPlace names to choose from; call again with one as location
locationNoName of the station or place the reading is for
temp_f_maxNoHigh end of today's range across the water body, °F
temp_f_minNoLow end of today's range across the water body, °F
distance_kmNoDistance from the requested coordinates to the station
observed_atNoISO-8601 UTC time the reading was taken
coverage_noteNoPresent when temp_f_min/temp_f_max describe a whole water body
data_freshnessNoISO-8601 UTC time the reading was fetched
needs_clarificationNoTrue when the name matched several places; see options

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/openWorld annotations, it discloses the live data provenance (NOAA CO-OPS, USGS, seatemperature.info), that results are not from training data, the nearest-station matching behavior for coordinates, and geographic coverage breadth. It also describes the needs_clarification result state, which is exactly the kind of behavioral detail annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability, then usage triggers, then the clarification protocol — a sensible order with almost no wasted wording. The coverage/geocoding sentence is somewhat dense and partially redundant with the coordinate guidance, keeping it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, and the description still covers input modes, data freshness, coverage limits, and the disambiguation edge case. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by framing location as an either/or with latitude+longitude, noting automatic nearest-station matching for coordinate inputs and string-to-coordinate geocoding as fallback. Some of this overlaps the schema's own 'nearest-station lookup' wording, so it is not purely additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get real-time water temperature and tide prediction data') and scopes it to named water bodies or lat/long coordinates. An agent immediately knows what this returns and for which locations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates trigger scenarios (swimming, boating, surfing, fishing, tide times, any real-time water question) and closes the loop on ambiguity with the needs_clarification flow: ask the user, then re-call with the chosen option. No sibling tools exist, so no alternative routing is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools