Related Servers

The tools are largely well-differentiated, and descriptions include explicit cross-references between overlapping workflows (e.g., swisstopo_oereb_at vs swisstopo_get_oereb_extract, swisstopo_map_query vs swisstopo_query_geodata). However, a few pairs could still be confused at the name level, such as swisstopo_map_query and swisstopo_query_geodata, or swisstopo_geocode and swisstopo_search_address, so it is not perfectly ambiguity-free.

Almost all tools use snake_case with the swisstopo_ prefix, and the '_at' suffix forms a clear pattern for coordinate-based lookups (municipality_at, zoning_at, oereb_at). Still, there are minor deviations like swisstopo_map_url, swisstopo_map_query, and swisstopo_elevation_profile, which lack the verb-object structure used elsewhere; the mixed get_/query_/search_ verbs also prevent a perfect score.

With 20 tools, the server is near the upper boundary of what is easy for an agent to navigate. The count is understandable for a national geodata platform covering geocoding, elevation, maps, OEREB, STAC downloads, and address lookups, but several tools could have been consolidated or layered more tightly.

The tool surface covers the main Swiss geodata workflows: geocoding and reverse geocoding, height and elevation profiles, coordinate conversion, map/feature queries, zoning, municipality and postal-code lookups, OEREB/EGRID, and downloadable STAC collections. Minor gaps exist, such as no direct tile/WMS URL generation or administrative boundary geometry retrieval except through swisstopo_map_query, but these are workable gaps rather than dead ends.