Skip to main content
Glama

CivicDataForge Public-Records Data

by io.github.equinoxaifinance-rgb
OverviewDiscussionsAdmin

US STR Permit Registry

civicdataforge--str-permit-registry

Use for address, permit-ID, or jurisdiction research across the supported US short-term-rental permit sources. For Florida statewide DBPR lodging licenses, use fl-dbpr-vacation-rentals instead. Address mode preserves explicit evidence decisions, scope, and receipts. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

Input Schema

NameRequiredDescriptionDefault
citiesNoWhich of the 55 city registries to pull (54 places; Honolulu publishes two). Published fields vary by city; see the README coverage table.
statusNoReturn all permits, or only currently-active licenses.all
snapshotNoPersist a query-scoped baseline and compare it with the prior complete run. Requires maxRecordsPerCity to be cleared; capped results are rejected so they cannot create false disappearance alerts.
maxRecordsPerCityNoCap records per city (leave empty for the full registry).
resolveJurisdictionNoUse coordinates and Census boundaries to distinguish an incorporated city from an unincorporated county area. Disable for a faster raw-source pull.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / cities / description
      Previous value: -"Which of the 29 covered cities to pull. Published fields vary by city — see the README coverage table."New value: +"Which of the 55 city registries to pull (54 places; Honolulu publishes two). Published fields vary by city; see the README coverage table."
    • changedInput schema / properties / cities / items / enum
      Previous value: -[
-  "seattle",
-  "orlando",
-  "new_orleans",
-  "denver",
-  "chicago",
-  "marin",
-  "norfolk",
-  "nashville",
-  "osceola_county",
-  "polk_county",
-  "austin",
-  "houston",
-  "sacramento",
-  "san_bernardino",
-  "bend",
-  "aspen",
-  "philadelphia",
-  "albuquerque",
-  "asheville",
-  "louisville",
-  "arlington",
-  "san_diego",
-  "scottsdale",
-  "huntington_beach",
-  "coconino",
-  "san_juan",
-  "chattanooga",
-  "boston",
-  "kansas_city"
-]New value: +[
+  "albuquerque",
+  "arlington",
+  "asheville",
+  "aspen",
+  "austin",
+  "bend",
+  "boston",
+  "chattanooga",
+  "chicago",
+  "coconino",
+  "denver",
+  "houston",
+  "huntington_beach",
+  "kansas_city",
+  "las_vegas",
+  "louisville",
+  "marin",
+  "nashville",
+  "new_orleans",
+  "norfolk",
+  "orlando",
+  "osceola_county",
+  "philadelphia",
+  "polk_county",
+  "sacramento",
+  "san_bernardino",
+  "san_diego",
+  "san_juan",
+  "scottsdale",
+  "seattle",
+  "columbus_ga",
+  "cook_county_mn",
+  "little_rock_ar",
+  "cody_wy",
+  "green_bay_wi",
+  "key_west_fl",
+  "covington_ky",
+  "shreveport_la",
+  "north_las_vegas_nv",
+  "summit_county_co",
+  "breckenridge_co",
+  "placer_county_ca",
+  "washington_dc",
+  "honolulu",
+  "honolulu_nuc",
+  "big_bear_lake_ca",
+  "clear_creek_co",
+  "corpus_christi_tx",
+  "cambridge_ma",
+  "belton_tx",
+  "bedford_tx",
+  "baldwin_county_ga",
+  "ruidoso_nm",
+  "long_lake_township_mi",
+  "south_haven_mi"
+]
    • changedInput schema / properties / cities / items / enumTitles
      Previous value: -[
-  "Seattle, WA",
-  "Orlando, FL",
-  "New Orleans, LA",
-  "Denver, CO",
-  "Chicago, IL",
-  "Marin County, CA",
-  "Norfolk, VA",
-  "Nashville, TN",
-  "Osceola County, FL",
-  "Polk County, FL",
-  "Austin, TX",
-  "Houston, TX",
-  "Sacramento, CA",
-  "San Bernardino County, CA",
-  "Bend, OR",
-  "Aspen, CO",
-  "Philadelphia, PA",
-  "Albuquerque, NM",
-  "Asheville, NC",
-  "Louisville, KY",
-  "Arlington, TX",
-  "San Diego, CA",
-  "Scottsdale, AZ",
-  "Huntington Beach, CA",
-  "Coconino County, AZ",
-  "San Juan County, WA",
-  "Chattanooga, TN",
-  "Boston, MA",
-  "Kansas City, MO"
-]New value: +[
+  "Albuquerque, NM",
+  "Arlington, TX",
+  "Asheville, NC",
+  "Aspen, CO",
+  "Austin, TX",
+  "Bend, OR",
+  "Boston, MA",
+  "Chattanooga, TN",
+  "Chicago, IL",
+  "Coconino County, AZ",
+  "Denver, CO",
+  "Houston, TX",
+  "Huntington Beach, CA",
+  "Kansas City, MO",
+  "Las Vegas, NV",
+  "Louisville, KY",
+  "Marin County, CA",
+  "Nashville, TN",
+  "New Orleans, LA",
+  "Norfolk, VA",
+  "Orlando, FL",
+  "Osceola County, FL",
+  "Philadelphia, PA",
+  "Polk County, FL",
+  "Sacramento, CA",
+  "San Bernardino County, CA",
+  "San Diego, CA",
+  "San Juan County, WA",
+  "Scottsdale, AZ",
+  "Seattle, WA",
+  "Columbus, GA",
+  "Cook County, MN",
+  "Little Rock, AR",
+  "Cody, WY",
+  "Green Bay, WI",
+  "Key West, FL",
+  "Covington, KY",
+  "Shreveport, LA",
+  "North Las Vegas, NV",
+  "Summit County, CO",
+  "Breckenridge, CO",
+  "Placer County, CA",
+  "Washington, DC",
+  "Honolulu, HI",
+  "Honolulu, HI (approved nonconforming use certificates)",
+  "Big Bear Lake, CA",
+  "Clear Creek County, CO",
+  "Corpus Christi, TX",
+  "Cambridge, MA",
+  "Belton, TX",
+  "Bedford, TX",
+  "Baldwin County, GA",
+  "Ruidoso, NM",
+  "Long Lake Township, MI",
+  "South Haven, MI"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Without relying on annotations, it discloses the operational profile: it starts a bound Apify Actor using the caller's APIFY_TOKEN, may consume Apify usage, blocks for up to 60 seconds, and caps output at 1,000 source-linked rows. The annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) already flag external side effects, and the description complements them with the token/cost/timeout specifics rather than repeating them.

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?

Four compact sentences, front-loaded with the routing decision before the operational caveats. The clause 'preserves explicit evidence decisions, scope, and receipts' is vague jargon that does little work, keeping it short of a 5.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does: at most 1,000 source-linked rows, with jurisdiction resolution behavior covered by the schema. The main remaining gap is that the promised address/permit-ID lookup paths have no interface representation, which could leave an agent unsure how to actually invoke them.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema, making 3 the baseline. The description adds essentially no parameter-level meaning beyond that, and its mention of an 'address mode' that has no schema parameter is more likely to mislead than clarify.

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 verb and resource: 'address, permit-ID, or jurisdiction research across the supported US short-term-rental permit sources', which tells an agent exactly what domain it covers. It also names the sibling it is not (fl-dbpr-vacation-rentals). It loses a point because the advertised 'address' and 'permit-ID' modes have no corresponding parameter in the schema, so the stated capabilities and the actual interface drift apart.

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?

Explicitly routes Florida statewide DBPR lodging license work to fl-dbpr-vacation-rentals instead, which is exactly the sibling-level disambiguation an agent needs. It does not address when to prefer this over civicdataforge-evidence-gateway or property-violations, so the guidance is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CivicDataForge Public-Records Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources