tapwatermap

get_water_system

Read-onlyIdempotent

EPA record for a single water system by its PWSID (e.g. 'VT0005053'): name, population served, source, and violations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pwsid": "<pwsid>"
    },
    "name": "get_water_system"
  }
}

Input Schema

Name	Required	Description	Default
`pwsid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds the specific data fields returned (name, population, source, violations), which is useful beyond the annotations. However, it does not mention additional behavioral traits like real-time data or error handling.

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?

The description is a single sentence that conveys the core purpose and output. It is front-loaded with the verb 'EPA record' and is free of extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single required parameter, good annotations, and no output schema, the description adequately covers the tool's functionality. It mentions the returned fields, which is sufficient for a simple retrieval tool.

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?

Schema description coverage is 0%, but the description provides an example PWSID ('VT0005053') and indicates it's a string identifier. This adds some meaning beyond the bare schema, but does not fully specify format or constraints.

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 it retrieves an EPA record for a single water system by PWSID, listing specific fields like name, population, source, and violations. This distinguishes it from sibling tools like search_cities or get_city_water.

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

Usage Guidelines3/5

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

The description implies usage for a specific water system by ID, but does not explicitly state when to use it vs alternatives like search or list_state_cities. No exclusions or conditions are provided.

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

All tapwatermap tools Inspect

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

Need Help?