An MCP server that provides temporary email inbox functionality for agents, allowing creation of disposable email addresses, message reception, and retrieval.
Four tools with clear verb-noun naming (create_inbox, list_messages, wait_for_message, get_message). All have descriptions (avg 180 chars, within 10-1024 baseline). Input schemas present with type definitions. However, parameter descriptions are missing entirely, LLMs cannot infer what 'local_part', 'since_id', or 'timeout_seconds' mean without explicit guidance. Output schemas are not documented in the tool definitions. Error handling is minimal (returns null for missing inboxes, but no recovery guidance). No tool annotations (readOnlyHint/destructiveHint). Composition is sound: tools chain logically (create → list/wait → get). Risk classification present (WRITE vs READ_ONLY) but not exposed to LLM.
Create a new inbox. Returns the email address to hand out, the local_part that identifies it in the other tools, and expires_at (unix seconds) after which the inbox stops receiving and reading.
Get one message, including its body. The id comes from list_messages. Returns null if there is no such message.
List messages received at an inbox, newest first. Bodies are not included; use get_message for one message. Returns null if no such inbox exists, and an empty array if it exists but has received nothing.
Wait for mail to arrive at an inbox and return it, so you do not have to poll list_messages. Use this right after handing the address to a site. Returns as soon as a message newer than since_id arrives; if none does, returns after timeout_seconds with timed_out true and no messages, and you can call again. since_id defaults to 0, which accepts anything the inbox already holds. timeout_seconds defaults to 45 and is capped at 55. Returns null messages if no such inbox exists.
Parameter descriptions missing for all tools. 'local_part', 'since_id', 'timeout_seconds', 'id' lack any explanation of what they control or expected format. LLMs cannot infer parameter semantics from names alone.
Output schemas not documented in tool definitions. Callers cannot know what fields to expect (e.g., does list_messages return 'received_at' as Unix timestamp or ISO string?). Forces LLMs to guess downstream field names.
Error handling lacks recovery guidance. Returning null for missing inbox gives LLM no hint whether to retry, create a new inbox, or ask the user. No actionable error messages.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2025-06-18+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Risk classification exists in metadata but is not exposed via MCP tool annotations, limiting client-side safety checks.
create_inbox has empty input schema ({}). While this is correct for a no-argument tool, the description should clarify that no parameters are needed and what the TTL/expiration policy is.