Skip to main content
Glama

usgswater

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

USGS Water MCP — wraps USGS National Water Information System (NWIS) REST services (free, no auth)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
28.4% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-usgswater
GitHub Stars
0
Server Listing
usgswater

TDQS

A4.1/5.0

Scored across 34 tools

Disambiguation3/5

Most tools have distinct, well-documented purposes, but the ask_pipeworx family overlaps heavily — ask_pipeworx_beta is explicitly stated to currently match ask_pipeworx exactly, so an agent has no reliable basis to choose between them. The entry-point cluster (ask_pipeworx vs ask_pipeworx_grounded vs deep_research vs discover_tools vs suggest_questions) is heavily differentiated only by lengthy prose, and the five polymarket_* tools require careful reading to separate. The USGS water tools (current_conditions, daily_values, find_sites) are cleanly distinct.

Naming Consistency4/5

All 34 names use consistent lower snake_case, so there is no case-mixing problem. However the pattern is not uniformly verb_noun: some are verb-first (discover_tools, resolve_entity, validate_claim), some noun-first (entity_profile, current_conditions, daily_values), and several carry arbitrary prefixes (pipeworx_, polymarket_). Readable and predictable enough, but not a strict single convention.

Tool Count3/5

34 tools is heavy and sits in the 'too many' band for a single server surface, with the ask_pipeworx triplet and the five polymarket tools feeling like internal/experimental variants that could be consolidated. On the other hand, most tools map to genuinely distinct capabilities (routing, grounding, memory, subscriptions, water data), so it is over-scoped rather than padded.

Completeness4/5

The gateway-side lifecycle is well covered: discovery, routing, grounded answers, entity resolution, comparison, change feeds, memory (remember/recall/forget) and subscriptions (subscribe/unsubscribe/list/recent_alerts). Gaps are minor — for the USGS-water surface there is no dedicated site-metadata or parameter-catalog lookup and no raw record fetch-by-URI tool, but agents can work around these.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • mcp-usgs-water-data

    higherpass
    A
    license
    A
    quality
    B
    maintenance
    Enables querying USGS water data including real-time and historical streamflow, gage height, and water temperature from USGS gauges across the United States.
    3
    MIT

  • USGS Water MCP

    pgiffy
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides access to real-time water data from the USGS Water Services API, allowing users to fetch instantaneous measurements like stream flow, gage height, temperature, and water quality parameters from thousands of monitoring stations across the US.
    3
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources