Skip to main content
Glama

List coverage

list_coverage
Read-only

List covered US cities and counties (ids, names, permit counts, newest permit date, and how often their records include zip, location, job value, contractor and phone), permit categories and prices. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered structurally. The description adds real value beyond that: it enumerates the response fields and flags the call as 'Free', which tells the agent there is no credit cost and what data shape to expect. It stops short of saying how large the result is or that it covers the full index in one call.

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?

One sentence, front-loaded with the verb and resource, with the returned fields compactly parenthesized and the cost signal placed at the end. No filler and nothing an agent needs is buried.

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?

For a no-argument, read-only listing tool with annotations and an empty schema, the description covers what is returned and the cost. The only minor gap is response scale/breadth (how many cities/counties come back, whether results are exhaustive), which an agent might want to know before rendering output.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the description over-promises optional filtering, which correctly matches the empty schema.

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?

Specific verb (list) plus a precise resource: covered US cities and counties, permit categories, and prices. The parenthetical enumeration of returned fields (ids, names, permit counts, newest permit date, field-completeness stats) makes it unmistakable that this is a coverage/metadata listing, not a permit search. It does not name a sibling tool explicitly, which keeps it just short of a 5.

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 rather than stated: an agent can infer this is the way to discover which geographies and permit categories are available before calling search_permits or count_permits. The word 'Free' signals a zero-cost call an agent can safely front-load, but there is no explicit when-to-use, when-not-to-use, or named alternative.

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.

Resources