Skip to main content
Glama

Get building permit filter values and coverage

get_permit_reference
Read-onlyIdempotent

Building permit filter values with labels: work types and their groups, statuses and stages, why-now codes, trades, construction types, building types (the same labels as get_project_types), value bands, sorts, date fields, and date ranges. facet narrows it to one block. facet="coverage" lists the states, counties, and cities that have permits, each with a permit count and entitled (whether this account's plan covers it). Building permits start with Utah, and more areas are being added through the end of 2026. Does not use credits.

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": "get_permit_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
facetNoOne block, or "all" (the default). "coverage" lists where permits are and which places the plan covers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: no credit consumption, the coverage facet's count and entitled semantics, and the dataset's Utah-first rollout through 2026. It doesn't describe response shape or pagination for the non-coverage blocks.

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 block enumeration is front-loaded and the operational notes (facet narrowing, coverage, credits, rollout) follow in logical order. It is slightly padded by listing all thirteen blocks when the enum already carries them, but every sentence still carries usable information.

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 single-parameter reference tool with full annotations and no output schema, the definition covers cost, scope, and what the coverage facet returns, which is the main ambiguity an agent would face. It leaves the return shape of the other facets implicit, but the 'values with labels' framing is adequate for a lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter and schema description coverage is 100%, with the enum and the 'all' default both documented in the schema. The prose adds only the mild clarification that a facet 'narrows it to one block' and what coverage returns, largely restating the schema description, so the baseline of 3 applies.

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 uses a concrete verb-plus-resource framing ('Building permit filter values with labels') and enumerates every block the tool returns, including work types, statuses, why-now codes, value bands, and date ranges. It also links the buildingTypes block to get_project_types, so an agent can place this tool against a known sibling without opening either schema.

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

Usage Guidelines4/5

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

It explains how to narrow output ('facet narrows it to one block') and singles out the coverage facet with its own purpose, plus a cost signal ('Does not use credits') that helps an agent decide whether to call it. It stops short of explicit when-not-to-use guidance or naming which sibling to call instead when an agent wants actual permits rather than reference values.

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