No user-submitted related servers found.
Scored across 6 tools
Datasets, maps, and SQL each occupy distinct tool territory, and get_map vs list_maps is clearly separated. The only mild overlap is get_features versus query, both of which retrieve row-level data, but the GeoJSON-paging vs analytical-SQL split is well explained.
Five tools follow a predictable verb_noun pattern (search_datasets, get_dataset_schema, get_features, get_map, list_maps), but the bare verb `query` breaks the pattern and is less self-describing.
Six tools is well-scoped for a read-only geospatial catalog/query server; each tool serves a distinct step in the discover-schema-inspect-analyze workflow with no filler.
The read-only surface covers search, schema/trust metadata, feature retrieval, SQL analysis, and map metadata, forming a coherent lifecycle. The notable gap is raster datasets, which have no retrieval path since get_features errors on them, and there is no way to create or modify maps (likely intentional for a read-only server).