No user-submitted related servers found.
Scored across 34 tools
Several tool pairs have almost indistinguishable boundaries: controlcenter_list_tools and controlcenter_list_available_tools both start servers and read their tool lists, while controlcenter_find_capability and controlcenter_tool_overview both report native-binding claims from system-explorer resolutions. controlcenter_list_governance also overlaps controlcenter_list_decisions on the decision index, so an agent must read detailed descriptions carefully to avoid selecting the wrong tool.
The controlcenter_ prefix and verb_noun pattern (list_*, describe_*, suggest_*, resolve_*) are applied consistently for the vast majority of tools. A few outliers such as controlcenter_actual_self_receipt, controlcenter_tool_overview, and controlcenter_status break the pattern, but they are rare enough that the naming remains predictable overall.
At 34 tools the surface is too large for an agent to navigate efficiently and is well above the 25-tool threshold. The broad domain explains some breadth, but the presence of several near-duplicate tools inflates the count and makes the set feel over-engineered.
For a read-only, advisory control plane, the surface is fairly complete: server discovery, stacks, profiles, resources, locks, permissions, decisions, skills, plugins, and invocation are all represented. Minor gaps remain, such as no detail view after listing skills, plugins, or bundles, but agents can usually work around these.