Skip to main content
Glama
Waterboards MCP Server

Waterboards MCP Server

Get a public water system profile

waterboards_get_water_system
Read-onlyIdempotent

Retrieve the profile and compliance/risk summary for one California public water system by PWS ID, including violations, SAFER status, and risk levels.

Instructions

Get the profile and compliance/risk summary of one water system.

Source: Gold view v_water_systems (California State Water Board SDWIS inventory + SAFER risk assessment). Refreshed when the pipeline reloads the open data; the result carries data_as_of.

The single result has system name, county, city, type, owner, source type, population, service connections, last sanitary survey, safer_status, is_failing, economic_status (DAC/SDAC), violation flags with analytes (primary/secondary MCL, E. coli, treatment technique, monitoring), risk levels by category, and source_url. has_risk_assessment is false when the system is not in the SAFER file, in which case the violation/risk fields are null (unknown, not "none"). This is a regulatory screening, not a tap-water safety determination.

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": {
      "pws_id": "<pws_id>"
    },
    "name": "waterboards_get_water_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
pws_idYesCalifornia public water system ID, e.g. CA0110005.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover safety (readOnly/idempotent/openWorld), and the description goes well beyond them: it discloses the data source and view, that results carry `data_as_of` and refresh only on pipeline reload, that `has_risk_assessment: false` means fields are null-by-ignorance rather than 'none', and explicitly bounds interpretation ('regulatory screening, not a tap-water safety determination'). That is unusually rich behavioral context.

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 with the one-line purpose, then provenance, then return contents, then the null-semantics caveat and the screening disclaimer. The enumerated field list is long but it is bounded and each element is informative; nothing reads as filler.

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?

Despite an output schema existing, the description supplies the semantics the schema cannot: provenance/freshness, the null-vs-none distinction, the meaning of has_risk_assessment, and an explicit interpretive caveat. An agent can call and correctly interpret this tool with no further context.

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?

One parameter with 100% schema coverage, including a regex pattern and an example. The description adds nothing about pws_id format or origin, so the schema does all the work; baseline 3 applies.

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?

States a specific verb (get), resource (profile/compliance/risk of ONE water system), and scope. The 'one water system' framing distinguishes it cleanly from sibling list/near-zip tools, and 'compliance/risk summary' separates it from the chemistry-focused siblings.

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?

Usage is implied by the single-system framing and the required pws_id, but the description never says when to pick this over waterboards_get_system_source_chemistry or the near-zip finders, nor does it state a prerequisite beyond having the ID. Adequate context, no explicit routing.

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