No user-submitted related servers found.
Scored across 22 tools
Every tool targets a distinct resource-action combination (e.g., entity_read vs entity_update, decision_log vs decision_check, plan_set vs plan_add). Overlapping areas such as semantic_recall vs audit_log and wrap_check vs wrap_auto are clearly differentiated by their descriptions.
The majority of tools follow a consistent noun_verb pattern (plan_add, decision_check, entity_read). A few names like wrap_auto, semantic_recall, and audit_log deviate slightly from this pattern, but the overall convention remains predictable and readable.
With 22 tools, the set is on the heavy side, falling within the 16-25 borderline range. While each tool serves a meaningful purpose, the number exceeds the ideal 3-15 range for a well-scoped server.
The surface covers the core domain well: entity CRUD (via entity_read/update), decision lifecycle (log, check, review, refresh), plan management (set, add, advance, read), risk assessment, and memory operations. Minor gaps like explicit entity deletion or plan step editing are workable through entity_update and plan_set, so there are no critical dead ends.