county_coverage
Covered counties, streams, buyers, data sources, methodology, and honest signal-density notes per stream. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
parcel-edge
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description should disclose behavioral traits. However, it only lists the output content ('Covered counties...') without indicating side effects, cost, or access restrictions beyond 'Free'. No mention of idempotency, rate limits, or auth requirements.
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?
The description is a single sentence that efficiently lists the key items. It is concise without wasted words, but the structure could be improved by breaking into a clearer statement (e.g., 'Returns coverage data including...').
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema or annotations, the description provides reasonable context for a simple data retrieval tool. However, it lacks details on output format, interpretation of signal-density notes, and how the data can be used.
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?
The tool has zero parameters, and the schema coverage is 100% (empty object). Per guidelines, the baseline for zero parameters is 4. The description provides context about the output but does not add parameter-level meaning since none exist.
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 provides coverage details including counties, streams, buyers, data sources, methodology, and signal-density notes. The content is specific and distinguishes it from sibling tools which focus on leads, flags, and reports.
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 is given on when to use this tool versus alternatives. The description only mentions 'Free' but provides no context for usage conditions or prerequisites.
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
A4/5.0
Disambiguation5/5
Each tool targets a distinct aspect of property data: permit windows, stalled projects, exemption flags, lien reports, overassessment leads (commercial vs single parcel), and county metadata. The descriptions clearly differentiate their purposes, with no functional overlap.
Naming Consistency5/5
All tool names use a consistent underscore_case pattern with descriptive noun phrases (e.g., construction_window_leads, exemption_flags). No mixed conventions or cryptic abbreviations are present.
Tool Count5/5
Seven tools provide a well-scoped set for the server's purpose (property analytics for various stakeholders). Neither too few nor too many—each tool serves a clear, distinct function.
Completeness4/5
The tool set covers core workflows for permit tracking, exemption auditing, lien analysis, and overassessment detection. Minor gaps exist (e.g., no general property detail lookup), but the server seems intentionally focused on lead generation and flagged issues.