Related Servers

Most tools are clearly separable by resource and action: transaction searches differ by administrative, radius, or polygon scope, and parcel tools distinguish area listing, prefix lookup, single-parcel resolution, and full dossier. The numerous get_transaction_* per-layer breakdown tools target distinct data layers, though the price/statistics group (get_price_statistics, get_price_distribution, compare_locations, get_market_overview) requires careful reading to avoid misselection.

Tool names are consistently snake_case and mostly follow verb_noun or get_/search_/list_ patterns, with predictable families such as get_transaction_*, search_*, and get_parcel_*. Minor deviations like search_by_area and search_by_polygon use a search_by_ structure rather than a pure verb_noun pattern, but they remain readable and consistent with the search family.

28 tools is heavy for an MCP server and exceeds the typical 3–15 range, which increases selection burden for an agent. However, the domain is unusually broad—transactions, parcels, enrichment layers, statistics, demographics, and infrastructure—so most tools are not redundant, even if the surface is borderline over-scoped.

The server covers a wide read-only surface: transaction and parcel discovery, parcel resolution and reporting, many property/environmental layers, price statistics, demographics, infrastructure signals, and value estimation. A minor gap is the absence of a single general transaction-detail tool that aggregates all per-transaction layers in one call, though search results provide core transaction fields and the per-layer tools cover the details.