Skip to main content
Glama
higherpass

mcp-usgs-water-data

by higherpass

find_sites

Discover USGS monitoring sites by name, location, or geographic area, returning station numbers for water data queries.

Instructions

Look up USGS station numbers (siteNumber) to pass to get_instantaneous_values - use this whenever you have a place or river name ("what's the flow of the Chattahoochee in Atlanta") rather than a station number. Returned siteNumber values vary in length - typically 8 digits, but 15 for many groundwater/well sites - pass them through to get_instantaneous_values exactly as returned; do not truncate or pad.

Exactly one major filter is required: sites, stateCd, huc, bBox, or countyCd

  • same rule and the same named {west, south, east, north} bBox object as get_instantaneous_values.

nameContains filters results CLIENT-SIDE after fetching, not on the request - the /site/ service silently ignores name-search parameters, so this NARROWS a major filter's results rather than replacing it, and cannot be used alone. Matching is case-insensitive (most USGS station names are uppercase, e.g. "CHATTAHOOCHEE RIVER AT ATLANTA, GA", but not all are), so match casually.

A broad major filter with no nameContains can return hundreds of sites - Georgia alone has 544 IV-reporting sites - so pair a broad filter (stateCd, a wide bBox) with nameContains when looking for a specific place, and prefer a narrower filter (countyCd, huc) otherwise.

Defaults to hasDataTypeCd:"iv" (only sites that report instantaneous values), since a site without IV data cannot be used with get_instantaneous_values. Also defaults to siteStatus:"active", unlike get_instantaneous_values (which sends no siteStatus default and so returns readings from ALL sites) - the same major filter can therefore list fewer sites here than get_instantaneous_values will actually return readings for. Pass siteStatus:"all" to see inactive/discontinued sites too. Results are capped at maxSites (default 50, maximum 500); when more match, truncated:true and totalMatched: show how many were found in total. The cap keeps the FIRST maxSites in USGS site-number order, which runs roughly by drainage basin - raising maxSites therefore returns a geographic slice, not a broader or more relevant sample. Narrow with nameContains or a tighter major filter instead of raising maxSites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hucNoHydrologic Unit Codes: either one 2-digit major HUC, or one or more 8-digit HUCs (up to 10 total). At most one 2-digit HUC per request; 8-digit HUCs can be combined freely.
bBoxNoBounding box in decimal degrees, as named fields (not a positional array) so west/south/east/north cannot be silently transposed. Area (east-west)*(north-south) must be <= 25 square degrees.
sitesNoUSGS site numbers, typically 8 digits (e.g. "01646500"), but 15 digits for many groundwater/well sites (e.g. "334207084254801"). Pass them exactly as find_sites returns them; do not truncate or pad. Site-name lookup (e.g. "Potomac River") is not supported directly - use find_sites to resolve a name to a site number first.
stateCdNo
countyCdNo5-digit FIPS county codes (state FIPS + county FIPS), e.g. "24031" for Montgomery County, MD.
maxSitesNo
siteTypeNo
siteStatusNoactive
nameContainsNoCase-insensitive substring match against station names, applied CLIENT-SIDE after fetching - the /site/ service silently ignores name-search parameters, so this NARROWS the results of the major filter rather than the request itself. Cannot be used without a major filter.
hasDataTypeCdNoOnly return sites that report this data type. Defaults to "iv" (instantaneous values), since a site with no IV data cannot be used with get_instantaneous_values.iv
Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers richly: discloses that nameContains is applied client-side after fetching and that the /site/ service silently ignores name-search params; explains result ordering (first maxSites in USGS site-number order by drainage basin); exposes the siteStatus default divergence from get_instantaneous_values; documents the capped results and truncated/totalMatched behavior.

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 long but every paragraph earns its place—each covers a distinct, non-obvious behavioral or usage topic. Front-loaded with the purpose and primary use case, then progressively deeper caveats. Slightly verbose in places but justifiably so for the complexity of the behavior being disclosed.

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?

For a 10-parameter tool with no annotations and no output schema, the description is remarkably complete. It covers filters, defaults, side effects (truncation, client-side filtering), return quirks (siteNumber length variance, truncating/totalMatched), and ordering semantics. No meaningful gap remains for the agent to make bad decisions.

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 60%, so the description adds moderate value. It clearly explains the crucial nameContains client-side behavior (which the schema already touches on, but the description expands with the 'cannot be used alone' and 'narrows rather than replaces' semantics) and the major-filter-required rule. It doesn't re-explain already-covered params like huc/bBox, appropriately relying on the schema for those.

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 opens with a specific verb+resource ('Look up USGS station numbers') and immediately ties it to a downstream consumer (get_instantaneous_values), distinguishing it from sibling tools. It gives concrete use cases (place/river name queries) that differentiate it from get_instantaneous_values and list_common_parameter_codes.

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?

Provides exhaustive when-to-use guidance: use when you have a place/river name rather than a station number; names get_instantaneous_values as the intended downstream consumer; explicitly contrasts siteStatus/default behavior with get_instantaneous_values; gives concrete strategy advice (pair broad filters with nameContains, prefer narrow filters otherwise) and tells when NOT to raise maxSites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/higherpass/mcp-usgs-water-data'

If you have feedback or need assistance with the MCP directory API, please join our Discord server