No user-submitted related servers found.
Scored across 7 tools
Most tools have clearly distinct purposes: record vs. supersede, search vs. conflict checking, and linking requirements. Minor overlap exists because list_constraints covers a subset of what search_decisions can return, and get_context_for_task also surfaces constraints, so an agent may occasionally hesitate between lookup and context tools.
All seven tools use consistent snake_case and are verb-first (record_decision, search_decisions, get_context_for_task, list_constraints, supersede_decision, check_conflicts, link_requirement). The pattern is predictable and none of the names are misleading.
Seven tools is well within the ideal 3–15 range for a decision and constraint management server. Each tool maps to a distinct operation, and none feels padded or redundant.
The surface covers the core ADR/constraint lifecycle: record, search, context retrieval, supersede, conflict checking, and requirement linking. Minor gaps exist, such as no direct get-by-id or delete/unlink operation, but supersede and search largely compensate for these.
