Skip to main content
Glama

CivicDataForge Public-Records Data

by io.github.equinoxaifinance-rgb

Florida DBPR Vacation-Rental Licenses

civicdataforge--fl-dbpr-vacation-rentals

Use for Florida statewide DBPR vacation-rental and lodging-license evidence. For municipal STR permits use str-permit-registry; for code violations use property-violations. 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

TableJSON Schema
NameRequiredDescriptionDefault
cityNoFilter by property location city (e.g. Kissimmee, Orlando, Destin). Leave empty for all.
countyNoFilter to one Florida county by property location (e.g. Orange, Osceola, Dade, Monroe, St. Johns). Leave empty for statewide.
statusNoCurrent = up to date with DBPR; Delinquent = license not renewed on time (expiry date has passed).all
maxRecordsNoCap total records returned (statewide is ~174k).
licenseTypeNoDBPR licenses vacation rentals as Condos (type 2006) or Dwellings (type 2007, incl. single-family homes & townhouses).all
nameContainsNoCase-insensitive substring match on the business name or licensee name.
proxyConfigurationNoThe state site blocks plain datacenter traffic; Apify Proxy is used by default. Switch to residential if datacenter IPs get blocked.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only convey open-world, read-only-false, idempotent-false, destructive-false. The description adds valuable behavior: starts an Apify Actor, 'may consume Apify usage', 'waits up to 60 seconds', 'returns at most 1,000 source-linked rows', and 'without modifying government records'. This is exactly the kind of operational context beyond structured annotations.

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?

Two sentences with no filler. The first sentence establishes purpose and alternatives; the second lists side effects and limits. Information density is high and front-loaded.

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?

Despite seven optional parameters and no output schema, the description covers purpose, scope, alternatives, side effects, timeout, output cap, and non-mutating character. This is sufficient for an agent to select and invoke the tool correctly; field-level detail is already in the schema.

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 description coverage is 100%, so the baseline is 3. The description adds useful operational context not present in the schema, notably the global 'at most 1,000 source-linked rows' cap that constrains maxRecords, and the 60-second wait. This earns a 4.

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?

States the exact use case ('Florida statewide DBPR vacation-rental and lodging-license evidence') and names neighboring tools for adjacent scenarios. It clearly distinguishes itself from str-permit-regustry and property-violations, so an agent can select it without opening schemas.

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

Usage Guidelines5/5

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

Description explicitly tells when to use the tool ('Use for Florida statewide DBPR vacation-rental...') and when not to use it ('For municipal STR permits use str-permit-registry; for code violations use property-violations'). This is direct routing guidance to alternatives.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

The domain-specific tools are clearly separated by record type, with explicit cross-references that reduce confusion between similar categories like Texas vs. multistate childcare or STR permits vs. Florida DBPR lodging. The main ambiguity is the broad evidence-gateway tool, which overlaps with several specialized query tools and could be selected instead of the more precise one.

Naming Consistency4/5

The domain tools follow a consistent civicdataforge-- prefix pattern, and the Apify utilities follow a get-/abort- verb pattern, making the overall set readable. Minor deviations include the awkward civicdataforge--civicdataforge-evidence-gateway duplication and the mix between noun-style domain tools and verb-style utility tools.

Tool Count5/5

With 14 tools, the set is well-scoped: ten specialized public-record query tools plus four Apify lifecycle/data-access utilities. Each tool has a distinct role, and the count is appropriate for the breadth of supported public records without feeling bloated.

Completeness4/5

The tool surface covers a broad range of public-record evidence categories and provides the necessary run, dataset, and key-value-store operations for working with results. Minor gaps include a lack of discovery tools for listing supported jurisdictions/sources and no general-purpose search across all record types, but the core evidence workflows are well covered.

Resources