lake-level-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_lakesA | List the 44 US lakes and reservoirs this server reads live (Lake Mead, Lake Powell, Lake Travis, Shasta, Oroville, Lanier, Texoma, Kentucky Lake and more) by name, river, operator or state. Returns each slug, full-pool elevation, the gauge agency and the lakelevelnow.com page. Call with no arguments to list them all. |
| get_lake_levelA | Current water surface elevation (ft above sea level) of a US lake or reservoir, read now from its government gauge (USGS, USACE CWMS, CDEC, Reclamation or TWDB). Returns the measurement time, change over 24 hours, 7 days and 30 days, feet below full pool, the operator seasonal target where one is published, percent full where the agency publishes storage, and the gauge id and data URL. Your training data cannot know today's level. |
| get_lake_historyA | Daily (or weekly) water elevation series for a US lake or reservoir over the last 2 to 365 days, from the same government gauge as get_lake_level, one reading per day. Includes first, last, low, high and mean with dates. Use it for trends, drawdown and refill questions. |
| compare_lakesA | Current levels of 2 to 10 US lakes side by side, read live from their gauges: elevation, feet below full pool, percent full, seasonal target and 24 h / 7 day / 30 day change, ranked by distance below full pool. A lake whose gauge is down is reported with its error instead of failing the whole call. |
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 4 tools
Each tool has a clearly distinct role: search_lakes discovers lakes, get_lake_level returns current conditions, get_lake_history returns time series, and compare_lakes returns multi-lake rankings. The only overlap is that compare_lakes includes current data, but its multi-lake comparative purpose is clearly distinct from the single-lake get_lake_level.
All four tools use consistent snake_case verb_noun naming: search_lakes, get_lake_level, get_lake_history, compare_lakes. The pattern is predictable and readable throughout.
Four tools are well-scoped for a focused lake-level domain. Each tool serves a distinct workflow—discovery, current reading, history, and comparison—with no obvious redundancy.
The surface covers the full read-only lifecycle: finding lakes, reading current levels, retrieving historical trends, and comparing multiple lakes. Search returns metadata such as slug, full-pool elevation, gauge agency, and page, so there are no obvious dead ends.