MCP server for sending emails and listing recent emails via SMTP/IMAP
EmailMCP has well-structured schemas and clear naming conventions. Both tools (send_email, list_recent_emails) follow verb_noun patterns and include complete input schemas with type definitions and parameter descriptions. However, tool descriptions are minimal (10-20 chars), falling below the 50-200 char baseline for LLM-optimized descriptions. Output schemas are documented via Pydantic models but not exposed in tool definitions. Error handling is present but lacks recovery guidance. Missing tool annotations (destructiveHint for send_email, readOnlyHint for list_recent_emails) and no confirmation pattern for the write operation.
List recent emails
Send an email
Tool descriptions are too brief (10-20 chars). LLM cannot determine when/why to select tool. Baseline is 50-200 chars with context on WHAT, WHEN, and prerequisites.
send_email lacks destructiveHint annotation and confirmation pattern. Irreversible operations (send, delete, publish) should support dry-run or confirmation to prevent accidental execution.
Error responses lack recovery guidance. HTTPException(500) with raw IMAP error string does not tell LLM what to do next. Should categorize as retryable/user-fixable/fatal and suggest next steps.
Output schemas (SendEmailResult, ListEmailsResult, EmailItem) are defined in code but not exposed in tool registration. LLM cannot see what fields to expect without calling the tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Missing tool annotations. send_email should have destructiveHint=true; list_recent_emails should have readOnlyHint=true. Annotations help LLMs reason about side effects and retry safety.