No user-submitted related servers found.
Scored across 4 tools
Each tool has a distinct role: check validates a change, scan lists rules, explain details one rule, and recommend proposes a rule set. There is mild overlap among the three read-only rule tools (scan and explain both report violating files), but descriptions make the boundaries clear enough to select correctly.
All four tools follow an identical archprint_<verb> pattern (check, explain, recommend, scan) with consistent snake_case and clear verb-based naming.
Four tools is slightly lean but each covers a distinct phase of the rule lifecycle (discover, understand, propose, validate). It is not bloated, though the small surface leaves little room for the write-side operations the domain implies.
The server covers reading rules, explaining them, recommending them, and checking changes, but has no tool to actually adopt/write rules even though archprint init, generate, and wire are referenced repeatedly in descriptions. An agent can recommend and validate but cannot complete the adoption lifecycle, a notable gap.