coverage_stats
Read-onlyIdempotent
What TapWaterMap covers: states, cities, total EPA violation records, and the data quarter/date.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
TapWaterMap
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnly, idempotent, non-destructive. Description adds context that it returns summary statistics, which is consistent and provides added value beyond annotations.
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?
Single sentence, front-loaded with the key point, no unnecessary words.
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?
Given no parameters and no output schema, the description adequately explains what the tool returns. It is sufficient for its simplicity.
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?
No parameters exist, and schema coverage is 100% (empty). Description is not required to elaborate on parameters. Baseline score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides coverage information about the dataset (states, cities, total EPA violation records, data quarter/date). It distinguishes itself from sibling tools that focus on specific queries or searches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like search or fetch. Does not specify prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation3/5
Some tools have overlapping purposes: search and search_cities both find cities by name, and fetch and get_city_water both retrieve detailed records for a city. However, descriptions differentiate them (e.g., search returns an id, search_cities returns counts and URL), so an agent can often pick correctly, but confusion is possible.
Naming Consistency2/5
Tool names mix conventions: single-word verbs (fetch, search), verb_noun (compare_cities, find_cities), and noun_noun (coverage_stats). There is no consistent pattern, and similar tools have different naming styles (e.g., search vs search_cities).
Tool Count5/5
10 tools is well-suited for querying EPA tap water data. Each tool serves a distinct purpose within the domain, and the count is neither too few (limiting functionality) nor too many (overwhelming).
Completeness4/5
The tool surface covers key operations: searching cities, retrieving records, comparing, filtering, explaining contaminants, and coverage stats. Minor gaps exist (e.g., no way to search contaminants by partial name), but core workflows are supported.