No user-submitted related servers found.
Scored across 24 tools
Most tools are clearly separated into curated domain lookups, generic layer queries, and portal discovery, but find_nearby_amenities and query_near_point overlap in spatial-nearest behavior, and count_features overlaps with aggregate for counting. These pairs require careful description reading but are still distinguishable.
The set overwhelmingly uses snake_case verb_noun with meaningful verbs like list, get, search, and query. Minor inconsistency: aggregate has no object noun, find_nearby_amenities uses find instead of search, and get_distinct_values is more of a query operation. Overall the pattern is predictable.
At 24 tools, the server is on the heavy side and falls within the 16-25 range that feels burdensome. The breadth of the GIS portal does justify many tools, but agents face a large surface to learn and select from, so the count is borderline rather than ideal.
For a read-only municipal GIS server, coverage is excellent: layer discovery, schema inspection, attribute and spatial queries, aggregation, map rendering, portal/app exploration, plus curated tools for air quality, cadastre, construction, heritage, amenities, and streets. Only minor gaps like full geocoding exist, and their workarounds are documented.
