No user-submitted related servers found.
Scored across 9 tools
Most tools have distinct purposes, but there are real overlaps: get_component vs get_component_context (both inspect a single component), and get_design_context vs get_component_catalog (both give a system overview). The descriptions mitigate this heavily with explicit cross-references ('for X, use Y instead'), keeping misselection risk low but nonzero.
Eight of nine tools use a clean get_<noun> pattern (get_component, get_token, get_conflicts, get_violations, get_inferred_rules, get_design_context, get_component_catalog, get_component_context). find_components is the lone deviation, but the search-vs-fetch distinction is meaningful and readable.
Nine tools is well-scoped for a read-only design-system inspection server. Each tool covers a distinct facet (catalog, discovery, component detail, tokens, rules, conflicts, violations, context) without redundancy in count.
The surface covers discovery, component lookup, token lookup, inferred rules, conflicts, and violations, giving broad lifecycle coverage for a read-only inspection role. Minor gaps exist (no explicit snapshot-compare or diagnostics tool outside get_design_context), but agents can work around these.