No user-submitted related servers found.
Scored across 15 tools
Most tools are distinct, but align_search is an explicit alias of align_ask (a true duplicate that an agent could pick arbitrarily), and several pairs require careful reading to separate: align_check_alignment vs align_get_related_decisions (both surface prior decisions before editing), align_check_drift vs align_stale_code, and align_get_decision_timeline vs align_get_topic_timeline. The descriptions do an unusually good job of drawing the boundaries, which keeps this above a 2, but the built-in duplication and near-overlaps mean misselection is plausible.
All 15 tools share the align_ prefix and snake_case, with a dominant get_<object> pattern for reads (get_decision_rationale, get_impact, get_conflicts, get_related_decisions). Deviations are the bare-verb tools (backfill, sync, scope) and the vague ask/search pair, which drop the noun and don't match the get_ style, but the set is still highly predictable.
15 tools sits at the top of the well-scoped range but each maps to a real capability in a decision-graph domain (capture, retrieval, conflict/impact analysis, drift, source sync/scope/backfill). The only clearly unearned slot is align_search, a redundant alias of align_ask.
The set covers capture, retrieval, timelines, conflicts, impact, drift, stale code, pre-change checks, and source management — a strong read/analysis surface. But it is read-and-create only: there is no tool to update, edit, archive, or delete a decision, and no tool to acknowledge or resolve a conflict, even though the timeline description advertises 'acknowledged or resolved' events as part of the lifecycle.