Skip to main content
Glama
GSA-TTS

mcp-server-usgs-nationalmap

by GSA-TTS

Find NHD Waterbodies & Areal Water Features

hydro_find_waterbodies
Read-onlyIdempotent

Find lakes, ponds, reservoirs, swamps, and areal water features intersecting a point, parcel, or bounding box using USGS National Map NHDPlus HR data.

Instructions

Find NHD waterbodies (lakes, ponds, reservoirs, swamps) and areal water features.

Queries NHDWaterbody (layer 9) and/or NHDArea (layer 8) polygons intersecting the geometry. Both carry gnis_name, ftype/fcode, areasqkm, and elevation.

Use when: "Is there a lake within this parcel?", "What reservoirs intersect this bounding box?", "Name the waterbody at this point."

Returns: { "finding": str, "waterbody": {count, truncated, features, provenance}, # if requested "area": {count, truncated, features, provenance}, # if requested "query_geometry": {"type": str, "crs_epsg": int} }

ftype/fcode are integer codes; ftype_label/fcode_label give readable names.

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.
feature_classNoWhich polygon layer(s) to query: 'waterbody' (lakes/ponds/reservoirs/swamps), 'area' (wide rivers/bays/rapids/dams), or 'both'. Default 'both'.both

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Description adds substantial behavior not in annotations: queries layers 8/9, intersects geometry, returns structured result, and lists exact error messages. Annotations already declare readOnly/idempotent, but this details the operational contract.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose, use-case list, compact return snippet, and error examples. Every section earns its place; no filler despite being longer than average.

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 read-only query tool with output schema and 4 optional params, the description is remarkably complete: target layers, coordinate alternatives, return shape, and failure modes. No critical gap for an agent to invoke it correctly.

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 covers 100% of parameters, so baseline is 3. Description adds layer mapping (NHDWaterbody layer 9, NHDArea layer 8) and clarifies the feature_class options, plus shared attributes returned. This is extra semantic value, though most parameter syntax remains in 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?

Opening line names exact targets ('NHD waterbodies ... and areal water features') with examples (lakes, ponds, reservoirs, swamps). This distinguishes from sibling hydro_find_waterways, which implies linear features, and the rest are distinct tools.

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?

Provides explicit 'Use when' examples (e.g., 'Is there a lake within this parcel?'). It gives clear contexts but doesn't state when NOT to use or name alternatives, so not a full 5.

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