compare_cities
Read-onlyIdempotent
Compare the EPA records of several cities side by side. Pass cities as 'City, ST' strings.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cities | Yes | e.g. ['Burlington, VT', 'Houston, TX'] |
tapwatermap
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, non-destructive. The description adds that it compares side-by-side and requires a specific format, but does not disclose return details or behavior beyond that. This is adequate but not extra valuable.
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?
Two sentences with no extraneous information. The first sentence conveys purpose, the second provides usage format. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, so the description should hint at what the comparison returns (a table? scores?). It only states 'compare... records' without specifying the output format or content, leaving the agent unsure of what to expect.
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 coverage is 100% with an example for the cities parameter. The description reinforces the format ('City, ST'), adding clarity beyond the schema's example. This is slightly above baseline.
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 the tool compares EPA records of multiple cities side by side, with a specific verb and resource. It distinguishes from siblings like get_city_water (single city) and coverage_stats (different data). The format guidance 'City, ST' removes ambiguity.
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?
The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention when-not or recommend other tools for single-city queries, which is important given the many sibling tools.
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
B3.4/5.0
Disambiguation2/5
Multiple tools have overlapping purposes: `search` and `search_cities` both find cities by name, and `fetch` and `get_city_water` both retrieve EPA records for a city. This creates ambiguity for an agent deciding which tool to use.
Naming Consistency3/5
Most tools follow a verb_noun pattern (e.g., compare_cities, get_city_water), but `fetch` and `search` are single-word imperatives without an object, breaking the consistency slightly.
Tool Count4/5
With 10 tools, the server is well-scoped for a data retrieval domain. Each tool has a distinct role, though some overlap could be consolidated, the count is reasonable.
Completeness3/5
Core operations (search cities, fetch records, compare, list states) are covered, but the redundancy between `fetch`/`get_city_water` suggests unclear boundaries, and there is no tool to search by water system name or list all contaminants.