No user-submitted related servers found.
Scored across 28 tools
Each tool has a distinct purpose targeting specific entity types (e.g., aerial features, monuments, conservation areas, heritage at risk) with clear separation between count, search, get, export, cross-reference, and mapping operations. Even overlapping functions like search vs. nearby are distinguished by documentation, minimizing confusion.
All tools use 'her_' prefix and snake_case, with most following a verb_noun pattern (e.g., 'her_search_monuments', 'her_get_aerial_feature'). A few outliers like 'her_capabilities', 'her_map', and 'her_nearby' deviate slightly, but the overall pattern is strong and predictable.
With 28 tools, the server covers a broad domain (multiple heritage datasets, search, count, get, export, cross-reference, mapping) without being bloated. Each tool has a clear role, and the count is appropriate for the comprehensive scope described.
The tool surface covers all essential operations for a read-only heritage data API: capability discovery, status checks, listing sources, searching/counting/getting details for multiple entity types, cross-referencing, exporting (GeoJSON, LiDAR), and mapping. No obvious gaps for the stated purpose.