Skip to main content
Glama
GSA-TTS

mcp-server-usgs-nationalmap

by GSA-TTS

Find NHDPlus Stream Gages

hydro_find_gages
Read-onlyIdempotent

Find NHDPlus stream gages intersecting a watershed, bounding box, or river reach. Returns gage details and drainage area for USGS hydrology analysis.

Instructions

Find NHDPlus stream gages intersecting a geometry (NHDPlusGage, layer 0).

Each gage links to NWIS via sourceid + sourceagency and reports the monitored drainage area (dasqmi, in SQUARE MILES) and reach location.

Use when: "What stream gages are in this watershed / bounding box?", "Which gage monitors this river reach?"

Because gages are point features, supply a Polygon or BoundingBox to find gages within an area (a bare point rarely coincides exactly with a gage).

Returns: { "finding": str, "count": int, "truncated": bool, "features": [...], # station_nm, sourceid, sourceagency, dasqmi (SQ MILES), ... "provenance": {...}, "query_geometry": {"type": str, "crs_epsg": int} }

NOTE: dasqmi is drainage area in SQUARE MILES (not sq km).

Error responses:

  • "Error: supply either lat+lon or geometry, not both (or neither)"

  • "Error: unsupported geometry type ..."

  • "Error: NHDPlus HR request failed: ..."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (WGS84). Use with 'lon'. Omit when supplying 'geometry'.
lonNoLongitude in decimal degrees (WGS84). Use with 'lat'. Omit when supplying 'geometry'.
geometryNoGeoJSON geometry object as a JSON string. Supported types: Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon, or BoundingBox shorthand {"type": "BoundingBox", "bbox": [minLon, minLat, maxLon, maxLat]}. All coordinates must be WGS84 decimal degrees. Supply either this OR lat+lon, not both. Gages are points, so use a Polygon or BoundingBox to capture nearby gages.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the readOnly/idempotent hints, the description extensively discloses behavior: the return payload structure, the unit clarification for dasqmi, explicit error messages, and the guidance about gage point sparsity affecting geometry choice. This is far richer than minimal annotation coverage requires.

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 well-structured with clear sections for purpose, usage, return values, units, and errors. While longer than the minimal example, each section provides necessary contract-level detail. Minor redundancy exists between the return structure and the unit note, but overall the information is dense and justified.

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 covers the full lifecycle of using this tool: what it does, when to use it, how to supply geometry, the exact return format, unit conventions, and error scenarios. With an output schema already present, the description adds no unnecessary return-value explanation and leaves no significant gaps.

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

Parameters3/5

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

The input schema already provides 100% coverage for all three parameters, including the mutual-exclusion rule and the recommendation to use Polygon/BoundingBox. The description only reiterates this guidance without adding new parameter-specific meaning, so the baseline score of 3 is appropriate.

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 'Find NHDPlus stream gages intersecting a geometry' and identifies the specific layer (NHDPlusGage, layer 0). It also explains the gage attributes (NWIS linkage, drainage area) and distinguishes this from sibling tools by focusing on gages rather than waterways or waterbodies.

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

Usage Guidelines4/5

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

The description includes an explicit 'Use when:' section with example queries and provides practical advice on using Polygon/BoundingBox because gages are point features. It does not explicitly name alternative tools or when-not-to-use cases, but the context is clear enough for an agent to choose correctly.

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/GSA-TTS/mcp-server-usgs-nationalmap'

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