No user-submitted related servers found.
Scored across 11 tools
Most tools are clearly distinct, but get_conformance and get_capabilities have some overlap in purpose (both describe server capabilities). However, get_capabilities maps to human-readable names, providing enough differentiation. Other tools like search_collections vs get_collection and search_items vs get_item are well separated.
All tool names follow a consistent verb_noun pattern using 'get_' or 'search_' prefixes with snake_case. The naming is predictable and uniform across the entire tool set.
With 11 tools, the server is well-scoped for a STAC API. Each tool serves a distinct purpose without being excessive or too sparse, covering the essential operations expected from a STAC catalog.
The tool set covers the standard STAC API surface including root, conformance, capabilities, collections, items, search, queryables, and aggregations. It also adds useful extras like data size estimation and sensor registry info, leaving no significant gaps for typical STAC workflows.