No user-submitted related servers found.
Scored across 17 tools
Each tool has a clearly distinct purpose: sending (send_message), replying (reply), drafting (create_draft/send_draft/delete_draft), reading (get_message/get_thread), listing (list_messages/list_sent), and auxiliary actions (mark_read, react, add_recipients, resolve_address, delivery_status, download_attachment, whoami, wait_for_message). Overlaps like send_message vs. reply vs. send_draft are explicitly differentiated in the descriptions, so an agent can reliably select the right tool.
The set is overwhelmingly snake_case and most names follow a verb_noun pattern (mark_read, list_messages, send_message, create_draft, download_attachment, resolve_address). Minor deviations such as the noun-only delivery_status and bare verbs reply/react are readable and unambiguous, but prevent a perfect uniform pattern.
At 17 tools, this is slightly above the ideal 3–15 range for a focused server. However, each tool maps to a distinct messaging operation (send, reply, list, get, thread, drafts, attachments, reactions, waiting) with no obvious redundancy, so the count is reasonable rather than bloated.
The core messaging lifecycle is well covered: sending, replying, listing, fetching messages and threads, drafts, attachments, reactions, delivery status, and waiting for inbound messages. Minor gaps include no explicit draft-editing operation (you must delete and recreate) and no message search/filtering, but these are workable given the domain’s immutable-message design.