No user-submitted related servers found.
Scored across 10 tools
Several tools appear to do the same thing: change claims to be the only way to modify the map, while revise also says it can change/correct/undo the map, and undo duplicates revise's undo action. query, report show, and draw all overlap around reading/rendering views, while capture, change, and report overlap around recording events or map state. Agents will struggle to choose correctly without trial and error.
All tool names are lowercase single imperative verbs, so the naming style is consistent and readable. The main weakness is that several are broad meta-verbs (query, change, revise) rather than predictable verb_noun names, making their semantics less obvious despite consistent formatting.
Ten top-level tools is a reasonable count on the surface, but each tool is actually a mega-dispatcher bundling many actions, so the effective tool surface is much larger and poorly scoped. The count hides substantial complexity rather than reflecting a clean, well-bounded set.
The surface broadly covers the apparent domain: reading/searching the map, creating/updating/linking/archiving/restoring items, sessions, reporting, publishing, proposals, backups, and drawing. Some lifecycle edges are unclear or buried in dispatcher actions, but there are no obvious severe gaps for the stated scope.
