No user-submitted related servers found.
Scored across 13 tools
Most tools target distinct operations, but there are blurry boundaries: hub_send vs hub_answer (both deliver messages), hub_inbox vs hub_history (similar message-retrieval with subtle read-marking difference), and hub_answer conflates advisor replies with task approve/changes. The hub_send description explicitly redirects task reports to hub_task update, implying overlap that agents could easily get wrong.
Every tool uses a predictable hub_ prefix with snake_case and short, consistent modifiers (hub_send, hub_inbox, hub_task, hub_agents, hub_status, hub_history, etc.). The ask/answer pair is a natural convention and no style mixing occurs.
13 tools is well within the healthy 3-15 range and each maps to a concrete chat workflow (messaging, task sheet, presence, files, roles, linking). No tool appears redundant filler; the surface is scoped to a single cohesive domain.
The domain of chat + task coordination is largely covered: send/read messages, history, presence, task lifecycle (view/add/take/assign/update), files, roles, and session linking. Minor gaps exist (no message edit/delete or search, no explicit task removal or completion-closing tool), but agents can work around these.
