Engentfy Parcels

Count parcels for ANY city-scoped question using an exact summary view. Always use this tool instead of `count_properties` when a count is scoped to a city. It returns an exact precomputed total plus the authoritative ZIP codes represented by that city in the parcel data. Never infer or assume a city's ZIPs from general knowledge. Matching uses the normalized uppercase `city_key`, so inconsistent source casing does not affect the result. If the city is absent, the response is empty and explicitly tells the caller to check spelling; never substitute guessed ZIP codes or a similarly named city.

count_by_city

Count parcels matching supported filters — e.g. county, ZIP, or subdivision. The `city` filter is unsupported for counting because city counts scan 10.8M rows and either time out or produce unreliable estimates (observed 31x low). Use `count_by_city` for any city-scoped count; it returns an exact precomputed total and the authoritative ZIP codes represented by that city in parcel data. For supported filters, attempts an exact count first. If the database statement times out, retries with a planner estimate and marks the response as approximate. At least one filter is required. Combine filters to narrow (e.g. county + subdivision, or zipcode + use_code). Note: counting by `subdivision` (matched against the legal description) is only supported together with a `county` — a statewide subdivision-name scan is too slow. County, ZIP, owner, and value/year counts work on their own.

count_properties

Get the full record for one HOA / community association by its doc number. Returns the association, its management company, the community association manager, and how many parcels are linked to it.

get_hoa_detail

Get the HOA / community association (and its manager) governing a parcel. Direct links exist only for HOA-owned parcels (common areas), because linkage is by owner name. For an individual home with no direct link, this tool (with infer=True, default) infers the HOA from association-owned parcels in the same appraiser neighborhood — clearly tagged as inferred. A parcel may return more than one association (e.g. a master + sub-association).

get_hoa_for_parcel

Get the FULL record for a single parcel by object_id. Returns every property field (identification, owner, fiduciary, all just/assessed/taxable values, building and land characteristics, legal description, roof estimates, geo centroid) plus a clean `sale_history` array and human-readable `county_name` / `dor_uc_desc`.

get_property

Get the FULL record for a parcel by its parcel_id (exact match). Same complete output as `get_property`. If a parcel_id is not unique statewide, pass `county` to disambiguate; if multiple still match, the matches are returned for you to pick an object_id.

get_property_by_parcel_id

Get the sale history for a parcel (most recent sale first). Returns the property's recorded sales with price, year/month, OR book/page, clerk number, and qualification/vacant-improved codes.

get_sale_history

List every queryable column of the parcels table with its type. Use this to discover valid `column` names (and types) for `query_parcels` and for the `use_code`/filter arguments elsewhere.

list_columns

Query parcels by ANY column(s) — a flexible filter over the whole table. Use this when the fixed search tools don't cover the field you need (e.g. township/range/section, neighborhood code, homestead values, roof area, market area, fiduciary, etc.). Call `list_columns` to see queryable columns. Each filter is an object: {"column": <name>, "op": <operator>, "value": <v>}. Operators: eq, neq, gt, gte, lt, lte (comparisons); like, ilike (text — the value is treated as a 'contains' match unless you include * wildcards); in (value = list); is (value = null/true/false). All filters are AND-ed. Tip: pair a broad text filter with an indexed one (county/city) for speed — scans over unindexed columns across 10.8M rows can be slow.

query_parcels

Search parcels by physical street address (case-insensitive partial match). Returns a summary list. Use the object_id of a result with `get_property` to retrieve the full record.

search_by_address