No user-submitted related servers found.
Scored across 30 tools
Descriptions actively steer callers between overlapping families (search_transactions vs search_by_area vs search_by_polygon; get_parcel_report vs per-layer get_transaction_* tools), so most boundaries are clear. However, with 30 tools and several near-neighbors (get_transaction_permits vs get_permits_in_area, estimate_value vs estimate_land_value), an agent still needs to read carefully to avoid misselection.
Nearly all tools use a predictable snake_case verb_noun pattern (search_transactions, get_price_statistics, get_transaction_flood, list_locations). The main deviations are the search_by_area/search_by_polygon forms and mixed estimate_* naming, but these remain readable and not chaotic.
The domain is broad, but 30 tools exceeds the recommended range and includes many per-layer transaction detail tools that largely duplicate what get_parcel_report returns. Several could be consolidated into a parameterized transaction-detail or parcel-report call.
The read-only surface is extensive: transaction search by place/radius/polygon, price statistics, parcel resolution and reporting, environmental layers, permits, planning, nature, farmland, valuation, demographics and infrastructure. A generic get_transaction(id) endpoint is notable by its absence, but the layer-specific and aggregate report tools cover most workflows without major dead ends.
