No user-submitted related servers found.
Scored across 47 tools
Most tools target distinct resources and actions, and the descriptions go out of their way to explain when to prefer workspace_chat over the raw JSON read tools (get_workspace_issues, get_workspace_slxs, search_workspace). Some residual overlap remains in the read/query cluster (search_workspace vs workspace_chat vs get_workspace_config_index) and among run_script vs run_script_and_wait vs run_slx, but the guidance largely resolves it.
Nearly all tools follow a predictable snake_case verb_noun pattern (get_*, list_*, create_*, update_*, delete_*, run_*, search_*). The main deviation is workspace_chat, which uses a noun_verb shape with no verb prefix, plus minor inconsistencies in the domain prefixing (get_workspace_chat_config vs list_chat_rules).
At 47 tools this is well past the point where a set feels heavy; several clusters could be consolidated (run_script + run_script_and_wait + get_run_status + get_run_output; the nine chat-rule/command tools; multiple overlapping workspace read tools). The domain is broad, but the surface is bloated beyond what each sub-area needs.
Coverage is strong: full CRUD for assistants, knowledge-base articles, and chat rules/commands, plus runs, registry, and discovery/codecollection workflows. Minor gaps exist (no create/update/delete for workspaces, only list_workspaces; no delete for chat rules) but the core lifecycles are represented.