Model Context Protocol server that gives any MCP client email fetching capabilities via IMAP
Four tools with complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (list_, fetch_, mark_, write_). Descriptions are present (avg 150 chars) but lack actionable context for LLM selection. Critical issue: no output schemas documented, LLMs cannot plan downstream calls. Parameters mostly typed but lack constraints (enums, ranges, formats). Error handling exists but provides minimal recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Composition is reasonable (each tool has one responsibility), but parameter descriptions are sparse.
Fetch the full content of a specific email by its unique UID returned from imap_list_unseen.
List all unseen emails in the INBOX. Returns a numbered list with unique UID, FROM, DATE, and SUBJECT for each email.
Mark one or more emails as seen by their UIDs. Pass UIDs as a JSON array, e.g. [46] for a single email or [42, 46] for multiple.
Save a draft email in the Entwurf folder. Pass recipient, subject, and body.
No output schemas documented. LLMs cannot infer what fields are returned or plan downstream tool calls. E.g., imap_list_unseen returns 'count' and 'emails' array with uid/from/date/subject, but this is only visible in code comments, not in tool metadata.
Parameter descriptions are minimal or missing. 'uid' in imap_fetch_email has a description, but imap_list_unseen has no parameters documented. imap_mark_seen's 'uids' description includes an example ('[46]') which LLMs may reuse literally. imap_write_draft's 'inReplyTo' and 'references' lack format guidance (should specify Message-ID format).
No tool annotations (readOnlyHint/destructiveHint/idempotentHint). imap_mark_seen and imap_write_draft are destructive/stateful, but the tool definitions do not declare this. LLMs cannot distinguish safe-to-retry tools from irreversible ones.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Error messages lack recovery guidance. Code throws generic errors like 'IMAP error: ...' or 'Search failed: ...' without suggesting next steps. E.g., if IMAP connection fails, should suggest checking credentials or retrying.
No pagination support. imap_list_unseen returns all unseen emails without limit or offset. Large inboxes could return hundreds of emails, exhausting context window and degrading LLM reasoning.