No user-submitted related servers found.
Scored across 36 tools
Several tools have explicitly overlapping purposes or are near-duplicates: end_meeting and leave_meeting are stated to be the same result, share_content and send_chat target the same chat channel, and status/capacity_status/booth_status/meeting_status all report status-like information. Transcript reading is split across get_transcript, tail_transcript, tail_lines, and wait_lines, which can easily cause misselection despite detailed descriptions.
Most names follow a snake_case verb_noun or clear noun pattern, such as list_meetings, create_broadcast, join_broadcast, end_broadcast, schedule_meeting, and update_schedule. Minor deviations like snapshot, status, mute, unmute, say, and tail_events are still readable and mostly fit the same lowercase snake_case convention.
With 36 tools, the surface is heavy for a broadcast/meeting bot and includes many narrowly scoped operations and status/transcript variants. While the domain is broad, the count exceeds what an agent can comfortably distinguish without extra tool-selection overhead.
The tool set covers meeting lifecycle, broadcast creation and hosting, scheduling, chat, speech, transcripts, capacity, and bot status, which is a fairly complete surface for the stated domain. Some gaps remain, such as no direct screen-sharing tool despite share_content being explicitly chat-only, but most core workflows have coverage.