Skip to main content
Glama

Mailbox MCP

by com.mailbox-mcp.mcp
OverviewDiscussionsAdmin

Check for delivery and read confirmations

check_receipts
Read-onlyIdempotent

Find the confirmations that came back for messages this mailbox sent. Two kinds arrive: a DELIVERY confirmation, meaning the recipient's SERVER accepted the message, and a READ receipt, meaning their mail program reported that the message was opened. Use it after sending something important, or when the user asks whether a message got there. Pass the messageId from a send result to ask about one specific message. WHAT A MISSING RECEIPT MEANS: NOTHING AT ALL, and you must say so rather than let the user read silence as "they ignored me". A read receipt only exists if the recipient's mail program offers one AND they agreed to send it - consumer Gmail never does, Google Workspace only if an administrator switched it on, and Apple Mail only if the person changed a setting that ships off. Most messages will never produce one even when they are read within minutes. A read receipt that DOES arrive means the message was opened, not that it was read or understood, and one reporting deleted means it was thrown away unopened. This finds a receipt only if the message ASKED for one: set requestReadReceipt on send_email when you send it. Nothing here can be requested retrospectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow far back to look, in days. Defaults to 7.
mailboxesNoFolders to scan. Defaults to INBOX and Junk.
messageIdNoOnly report confirmations for this message, using the `messageId` a send result gave you. Leave it out to see everything that came back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description thoroughly explains the meaning of missing receipts, the conditions under which read receipts exist, and the semantics of a 'deleted' status. This goes well beyond the readOnlyHint annotation and provides critical expectations for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well structured, starting with purpose, then usage, then caveats. It is somewhat lengthy, but every sentence carries important operational nuance, so the verbosity is justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the conceptual output and edge cases, but since there is no output schema, it does not explicitly enumerate the returned fields or format. This leaves a small gap, though the mention of statuses like 'deleted' gives some indication.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers all parameters at 100%, and the description adds valuable context for messageId by referencing send results and explaining the default behavior when omitted. Days and mailboxes are well covered by schema descriptions, though the tool description does not add much beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: finding delivery and read confirmations for sent messages. It distinguishes between the two receipt types and differentiates this tool from related siblings like check_bounces and list_emails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is given for when to use the tool: after sending something important or when the user asks whether a message arrived. It also explains when not to expect results, noting that receipts must have been requested at send time and cannot be requested retroactively.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mailbox MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources