river-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 |
|---|---|
| find_river_gaugesA | Search USGS stream gauges nationwide by river and place name (for example "mississippi st louis", "potomac little falls"), by state, or within a radius of a latitude and longitude. Returns site numbers with whether each is reporting now and its latest stage and flow, active gauges first. |
| get_river_levelA | Current river stage (gage height in feet), streamflow (discharge in cubic feet per second) and water temperature where measured, read now from a USGS stream gauge (readings every 5 to 60 minutes). Adds the NWS flood stages (action, minor, moderate, major), the current flood category, feet below flood stage and the record crest when the gauge is an NWS forecast point. Flags readings over 48 hours old. Your training data cannot know today's river level. |
| get_river_historyA | Daily mean streamflow (default) or stage for a USGS gauge over the last 2 to 366 days, with first, last, low, high, mean and change. Use it for trend, drought and "is the river rising" questions. Many gauges publish daily means for discharge only. |
| get_flood_forecastA | The current NOAA National Water Prediction Service river forecast for a gauge: the forecast stage and flow series, the forecast crest with its flood category, the latest observation, flood stages and the record crest. Works for NWS forecast points (accepts the NWS id or the USGS site number). Forecasts are reissued several times a day. |
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 maps to a distinct temporal/functional role: find_river_gauges for discovery, get_river_level for current conditions, get_river_history for past trends, and get_flood_forecast for predictions. The only minor overlap is that get_river_level and get_flood_forecast both surface flood stages, but the primary purpose of each is clear and an agent can select confidently.
All tools follow a clean verb_noun pattern (find_river_gauges, get_river_level, get_river_history, get_flood_forecast) with the river/gauge domain object consistent across names. The find-vs-get distinction is semantically meaningful (search vs. retrieve) rather than arbitrary.
Four tools is well-scoped for a focused USGS gauge data server: discover, current reading, history, and forecast. Each earns its place with no redundant or filler tools.
The surface covers the full read lifecycle from gauge discovery through current readings, historical trends, and NWS forecasts, which addresses the common question types. Minor gaps remain, such as comparing multiple gauges in one call or basin-wide summaries, but agents can work around these via repeated queries.