Related Servers

Each tool maps to a distinct resource+action: agents (list/get), registration (register/unregister), direct messaging (send_message/read_conversation), inbox+mentions (read_inbox), channels (post/read_channel/list_channels/join/leave), plus status, delivery tracking, and two blocking waits. The main soft spot is the read surface, where read_inbox, read_conversation, read_channel and search all 'read messages' but differ by scope; descriptions disambiguate them well, but an agent must read carefully. wait_for_mail versus ask is also close, though ask is clearly the send-and-block variant.

Predominantly verb_noun (list_agents, get_agent, send_message, set_status, read_inbox, read_conversation, read_channel, list_channels, join_channel, leave_channel, wait_for_mail, message_status). A handful of bare verbs (register, unregister, ask, search, post) break the pattern, but they are conventional single-word actions and remain readable. No camelCase/snake_case mixing.

17 tools is slightly above the comfortable range but each covers a real capability of a multi-agent messaging system (identity, DMs, inbox, channels, membership, status, blocking waits). Nothing looks redundant enough to cut. It is on the heavy side for an agent to hold in context, which keeps it from a 5.

Covers the full lifecycle: register/unregister, agent directory, send/receive DMs, inbox with mentions, channel post/read/list/join/leave, search, status, and read receipts. Gaps are minor and partly intentional (no edit/delete of messages or posts, no tool to manage operator-added people, no explicit mention-listing tool since mentions fold into read_inbox). Agents can work around these without dead ends.