No user-submitted related servers found.
Scored across 15 tools
Each tool maps to a distinct resource+action: reading (list_messages, read_message, get_attachment), composing (send_message, reply_message, forward_message, respond_to_invitation), housekeeping (mark_message, delete_message), and calendar lifecycle (create/update/cancel/get/list events). The only plausible overlap — answering an invitation versus replying to a mail — is explicitly disambiguated in the descriptions ("do not answer invitations with send_message", "use get_event for one event"). Retrieval pairs like list_events/get_event and list_messages/read_message are cleanly separated.
All 15 tools follow a consistent snake_case verb_noun pattern (list_messages, read_message, send_message, create_event, cancel_event, get_attachment). The only mild variance is the verb choice between read_message and get_event/get_mailbox_info for single-item retrieval, but the structure is fully predictable. No camelCase or vague bare-verb names.
15 tools sit at the upper end of the ideal range but each earns its place: 3 for reading, 4 for composing, 2 for mailbox housekeeping, and 6 for the calendar sub-domain. The mail+calendar scope justifies the breadth; nothing looks redundant or padded.
Core lifecycle is covered end to end: discover policy, list/search/read, download attachments, send/reply/forward, mark/delete, plus full event create/update/cancel/get/list and invitation responses. Minor gaps remain — no tool to read the Sent folder despite send_message writing there, no folder/label/archive management, and no way to restore a message from Trash — but agents can work around these.