No user-submitted related servers found.
Scored across 42 tools
Most tools target a distinct resource+action (song vs section vs event vs user), and the parallel export/comment/reorder tools are clearly scoped by their noun. Minor overlap exists between vibo_get_me and vibo_healthcheck (both fetch the current user) and between vibo_comment_on_song and vibo_update_song's comment field, but these are distinguishable from descriptions.
Names consistently use the vibo_ prefix with snake_case verb_noun patterns (get_event, list_sections, add_song_to_section, delete_song_comment). Slight deviations like vibo_healthcheck (noun) and vibo_get_me (verb+pronoun) are minor and don't impede readability.
At 42 tools the surface is heavy, well above the 16-25 borderline band, and covers many parallel resources (songs, sections, questions, users, notifications, playlists, exports) in one flat list. The scope is broad but the count feels inflated and increases selection cost for an agent.
Coverage spans the full domain lifecycle: events (list/get/join/leave/create contact/invite/role change/remove), sections (CRUD, reorder), songs (add/remove/update/reorder/move/like/comment), planning questions, notifications, playlists and profile. Only minor gaps remain (e.g. no explicit event create/update), which agents can mostly work around.