Skip to main content
Glama

usgs-water-mcp-server

by io.github.cyanheads

Water Get Conditions

water_get_conditions
Read-onlyIdempotent

Get a USGS site's current reading ranked against its full period-of-record daily-mean percentiles for the same calendar day — a "how unusual is this" percentileClass (record-high to record-low), not a flood-stage or drought determination (this tool fetches no authoritative thresholds). The reading is instantaneous but the percentiles are daily-mean, so the ranking is approximate (see historicalContext.comparisonBasis). When the record is too short to rank, returns the reading with historicalContext=null instead of an error. Use water_find_sites and water_list_parameters to resolve inputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesUSGS site number (8–15 digits, e.g. "01646500" for Potomac River at Little Falls). Use water_find_sites to discover valid site numbers.
parameterCdYes5-digit USGS parameter code (e.g. "00060" for discharge, "00065" for gage height). Use water_list_parameters to discover codes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoInformational note explaining why historicalContext is null or incomplete. Absent when full historical context is available.
errorNoPresent when the call failed. Absent on success.
siteNameNoHuman-readable USGS site name.
unitCodeNoUnit of measure for currentValue and the historical percentiles (e.g. "ft3/s", "ft").
qualifiersNoData qualifier codes for the current reading.
siteNumberNoUSGS site number (8–15 digits, e.g. "01646500").
parameterCdNo5-digit USGS parameter code that was queried (e.g. "00060").
currentValueNoMost recent observed value as a string. Empty string when no data is available for the current period.
parameterNameNoHuman-readable parameter name with units (e.g. "Streamflow, ft³/s").
currentDateTimeNoISO 8601 date-time of the most recent observation.
historicalContextNoHistorical percentile context for the observation's calendar day. Non-null only when historicalContextStatus is "available"; see that field for why it is otherwise absent.
historicalContextStatusNoWhy historicalContext is or is not populated. 'available': percentiles for the observation's calendar day are present. 'no_matching_day': the stat table has rows but none for that calendar day. 'no_record': the stat table is empty — a new site, or a record too short to compute percentiles. 'unavailable': the statistics service call failed — a transient upstream error, not a statement about the site's record; retry shortly.

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses important behavioral nuances: the reading is instantaneous while percentiles are daily-mean (hence approximate), and that a null historicalContext is returned for short records instead of an error. This goes beyond the read-only and idempotent annotations, providing critical expectations.

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?

The description is a single, well-structured paragraph that conveys all necessary information without redundancy. While it is fairly long, every sentence contributes meaning, covering the core function, limitations, and fallback behavior.

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?

The description fully equips an agent to use the tool correctly: it explains the metric, the approximation, the null case, and points to sibling tools for input discovery. Given the output schema exists, the absence of output details is acceptable.

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?

The schema already fully describes the parameters (site and parameterCd) with patterns and examples. The description adds value by advising the use of water_find_sites and water_list_parameters to resolve valid values, enhancing parameter semantics beyond the schema.

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?

The description clearly states the tool's purpose: retrieving a current reading ranked against daily-mean percentiles, explicitly distinguishing it from flood/drought assessments. It names specific resources (USGS site, parameter code) and contrasts with sibling tools.

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?

It explicitly states when to use the tool (when percentile ranking is needed) and when not to (not for flood-stage or drought determination). It also directs users to water_find_sites and water_list_parameters for input resolution, giving clear contextual guidance.

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

All usgs-water-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: site discovery, parameter lookup, instantaneous readings, time series, conditions, and dataframe analysis. No overlapping functionality.

Naming Consistency4/5

All tools start with 'water_' and mostly follow a verb_noun pattern (e.g., water_find_sites, water_get_readings). The dataframe tools (water_dataframe_describe, water_dataframe_query) use a noun_verb structure, which is a minor deviation.

Tool Count5/5

7 tools is well-scoped for the domain, covering essential operations without excess or deficiency.

Completeness4/5

The set covers key workflows: site discovery, parameter lookup, data retrieval (instantaneous, series, conditions), and analysis. Missing a dedicated tool for detailed site metadata, but find_sites provides reasonable coverage.

Resources