Skip to main content
Glama
Waterboards MCP Server

Waterboards MCP Server

Get source chemistry for a water system

waterboards_get_system_source_chemistry
Read-onlyIdempotent

Retrieve recent source-water chemistry for a California water system's wells, including chemical results, sample dates, and optional chemical and detected-only filters.

Instructions

Get latest source-water chemistry for one water system's wells.

Source: Gold view v_source_chemistry_latest (DDW/GAMA drinking water source chemistry, 2020 to present). Refreshed when the pipeline reloads the open data; each result has last_observed. Ordered by chemical, then well. Get pws_id from waterboards_find_water_systems_near_zip.

chemical is a case-insensitive name fragment; detected_only skips non-detects.

Each result is the latest sample for one well and chemical: pws_id, system_name, well_id, chemical_name, result_numeric, units, reporting_limit, is_non_detect, last_observed (sample date), sample_count, and source_url. When is_non_detect is true, result_numeric is null and the chemical was not found above reporting_limit. This is raw source water before treatment, not tap water, and not a health determination; units vary by chemical (UG/L, NG/L, MG/L, ...) so never compare across units.

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_system_source_chemistry"
  }
}

Input Schema

NameRequiredDescriptionDefault
pws_idYesCalifornia public water system ID, e.g. CA0110005.
chemicalNo
paginationNo
detected_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the underlying 'Gold view v_source_chemistry_latest' provenance, refresh cadence, result ordering (chemical, then well), non-detect semantics (result_numeric null when is_non_detect is true), and a critical units caveat warning against cross-unit comparison.

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?

Front-loaded with purpose, then provenance, then parameters, then result semantics in clearly separated paragraphs. Dense but every sentence carries operational value (units warning, non-detect semantics, source tool); slightly long, but nothing is 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?

An output schema exists, so return values need not be enumerated, yet the description goes further and explains how to interpret the key fields. Combined with provenance, ordering, the non-detect rule, and the pre-treatment/units caveats, an agent has everything needed to call and correctly interpret this tool.

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 description coverage is only 25%, but the description compensates for the two non-obvious parameters: 'chemical' is clarified as a case-insensitive name fragment, and 'detected_only' is defined as skipping non-detects. It also explains where pws_id comes from, though it says nothing about the pagination limits/offset beyond what the schema documents.

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?

Opens with a specific verb+resource+scope: 'Get latest source-water chemistry for one water system's wells.' That scope ('one water system') cleanly separates it from the sibling waterboards_get_source_chemistry_near_zip and from waterboards_get_tap_water_for_zip, which the description also explicitly contrasts against.

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

Usage Guidelines5/5

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

Explicitly routes the agent to waterboards_find_water_systems_near_zip to obtain the required pws_id, and states when the result is not appropriate ('not tap water, and not a health determination'), which tells the agent to reach for the tap-water sibling instead in those cases.

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