Skip to main content
Glama

Get building permits saved on a list

get_list_permits
Read-onlyIdempotent

Building permits already saved on a named list. get_list returns the list and its permitCount before this read. Extra filters such as workTypes, statuses, and valueMin apply inside those existing permits. limit is required. Each new or changed permit counts toward 100,000 export records a month on County, State, and National plans. On API Only and the trial, costs 1 credit per new or changed permit. An unchanged permit already delivered does not use credits. create_permit_export with this listId queues a CSV of the same set. contactWithheld on a private individual means the phone or email exists but is withheld: "upgrade" (homeowner phones and emails need a paid plan, and the user's plan does not include them) or "acknowledge" (the user accepts the homeowner contact rules once in the Boardwalk web app). It is never missing. "[phone withheld]" and "[email withheld]" in titles, summaries, or notes (textContactWithheld) are the same rule and can hide business lines too. Name every party; mention withholding only for a party that carries contactWithheld.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>",
      "limit": "<limit>"
    },
    "name": "get_list_permits"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSame as the permits map search box: words from the permit (work description, address, names) or a permit number. One search text, not a list: for several alternative terms, make one call per term. Use one of q, permitNumber, or contractor per call.
idsNoAlias of permitIds.
bboxNoMap area as "west,south,east,north" or {west,south,east,north}. Around a planned project, search q with its street address first; use a small box around its coordinates only when it has no address, and say which permits are at neighbouring addresses.
limitYesRequired. Number of records to return, 1-25. Each new or changed record counts toward 100,000 export records a month. An unchanged record already delivered does not.
citiesNoRegion: city ids or names ("Lehi"). A permit in any listed state, county, or city matches, so do not add the county. A name that matches several cities is refused with each candidate's id and state: pass the id, or add the state (states:["UT"]), which then only helps find the city.
dateToNoWindow end, YYYY-MM-DD, inclusive.
listIdYesThe list's public id ("lst_…"), from list_user_lists.
offsetNo
stagesNoStatus stage as "<status>:<stage>" or "bucket:<status>"; get_permit_reference facet "stages" lists them.
statesNoRegion: state ids, names, or abbreviations ("UT"). states, counties, and cities are one Region filter: a permit in any of them matches. Send only the narrowest place, never "UT" together with "Utah County".
tradesNoTrades the job involves (the scope of the work, not open bids): site_work, foundation, paving_concrete, framing, roofing, windows_doors, siding_exterior, insulation, electrical, plumbing, hvac, gas, fire_protection, low_voltage, solar, elevator, drywall, flooring, cabinets_countertops, finish_carpentry, painting, appliances, cleaning, landscaping, fencing, pool. roofing here also matches new homes and additions with roof work; workTypes roofing is re-roof jobs only. When a trade rep asks for "roofing permits", count both and say which is which.
whyNowNoWhy now codes: issued_no_inspections, rough_in_passed, finals_next, last_inspection_failed, on_hold, fees_due, slow_review, new_owner, expiring_soon.
sectorsNoPrivate or public work. Default both.
sqftMaxNoSquare feet maximum.
sqftMinNoSquare feet minimum.
countiesNoRegion: county ids or names ("Utah County"). Names that match more than one place are refused, not guessed; the refusal lists each candidate's id and state. A permit in any listed state, county, or city matches. A state sent with a county inside it only helps find the county (warning region_parent_state_dropped).
dateFromNoWindow start, YYYY-MM-DD, inclusive.
jobKindsNoMajor or minor jobs. Default both; "major" alone leaves out small jobs such as a water heater swap.
placeKeyNoplaceKey from a permit: every permit at that address (at most 20 keys).
statusesNoStatus: in_review (applied or approved, not issued yet), active (issued, under way, or on hold), final (completed or closed), inactive (ended without a final: expired, withdrawn, denied, void, or stopped), no_construction (a record with no construction work).
unitsMaxNoUnits maximum.
unitsMinNoUnits minimum (homes or apartments on the permit).
valueMaxNoJob value maximum in dollars.
valueMinNoJob value minimum in dollars, as stated on the permit. "Over $50k" → 50000.
dateFieldNoWhich date the window applies to: applied, issued, or activity (latest activity, the default).
dateRangeNoDate window. Defaults to 12m. "all" removes the window.
permitIdsNoExact permit ids to re-read, at most 100. No default date window applies. Unchanged permits already delivered are not charged again.
workTypesNoWork type keys: new_home, multifamily, adu, manufactured, new_commercial, new_other, addition, interior_remodel, kitchen_bath, tenant_improvement, accessory, structural_repair, repair, hvac, electrical, solar_battery, generator, plumbing, water_heater, gas, fire_protection, telecom, roofing, windows_doors, siding, pool, fence, signage, demolition, grading, utilities, driveway_sidewalk, septic_well, planning, unspecified. A work type is what the job is: roofing = a re-roof or roof repair job. For every job that includes a trade (a new home includes roofing), use trades.
contractorNoA contractor's full name, e.g. "Acme Roofing". Case, punctuation, and endings such as LLC, Inc., Corp., Co., and Ltd. are ignored, so "acme roofing" also finds "Acme Roofing, LLC". Every other word counts, so part of a name ("Acme") matches nothing. When unsure of the name, call search_permit_contractors (q with the name words) and pass its contractorKeys.
detailOnlyNoOnly permits whose full detail page was read.
maxCreditsNoOptional ceiling on credits this call may spend (API Only and the trial). The API refuses rather than exceed it.
valueBandsNoValue bands: u10k (under $10k), 10k, 50k, 250k, 1m (and up).
workGroupsNoWork type groups: new (new homes and buildings), remodel, systems, exterior, site, planning, unspecified.
assetClassesNoBuilding type class (3rd level), e.g. Single-Family Home.
permitNumberNoAn exact permit number, e.g. "BLD-2025-01234". Searches every date unless you send a date filter.
hasAnyContactNoOnly permits with any phone or email, private individuals included.
hasContractorNoOnly permits that name a contractor.
propertyTypesNoBuilding type, the same labels as planned projects (get_project_types): Residential, Commercial, …
contractorKeysNoExact contractor keys from search_permit_contractors (at most 50). Every permit by those contractors.
hasInspectionsNoOnly permits with at least one inspection that has a result (passed, failed, or completed).
includeRecordsNoAlso return non-job records (paperwork on an existing building). Default false.
propertySubtypesNoMore-specific building type (2nd level).
constructionTypesNoConstruction type: new_building, addition, renovation, site_work, infrastructure, demolition_only, none, not_stated.
hasCompanyContactNoOnly permits with a company phone or email printed on them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial beyond them: monthly export-record caps by plan, 1 credit per new or changed permit on API Only and trial, no charge for unchanged delivered permits, and required limit. It also explains how contactWithheld and "[phone withheld]" markers should be interpreted and reported, which is real result-interpretation context not present in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose, prerequisite, and export alternative are front-loaded, which is good. However, roughly half the text is a lengthy contactWithheld exposition that partly duplicates schema parameter descriptions, and the credit rule ("unchanged permit does not use credits") is restated in both the description and the limit schema entry.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 44-parameter read tool with no output schema, the definition covers the scope boundary, prerequisite call, credit/billing behavior, and the one output value that most needs interpretation (withheld contact). Little that an agent needs in order to call and interpret this correctly is missing.

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 98%, so parameters are largely self-documenting, but the description adds a genuinely non-obvious semantic point: the filters (workTypes, statuses, valueMin) constrain the permits already on the list rather than searching the whole database. It also flags that limit is mandatory, though that repeats the 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?

States a specific resource and scope: permits "already saved on a named list", with any extra filters applying "inside those existing permits". It separates itself from get_list explicitly ("get_list returns the list and its permitCount before this read") and from create_permit_export ("queues a CSV of the same set"), so the agent can distinguish it from the closest siblings.

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?

Gives a clear precondition (call get_list first to see the list and permitCount) and names a sibling alternative (create_permit_export with the same listId) for CSV output. It does not explicitly rule out the broader search_permits or count_permits paths, so the when-not guidance is incomplete.

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