Skip to main content
Glama

Mailbox MCP

by com.mailbox-mcp.mcp
OverviewDiscussionsAdmin

Release claimed emails

release_email
Idempotent

Let go of messages you claimed with claim_email, so a colleague can take them. Releases only your own claims: a message held by somebody else is left alone and the result names them, unless you pass force: true, which also clears a claim whose holder is no longer recorded. A message nobody holds is reported, not an error. Moves nothing and marks nothing read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidsYesThe UIDs to act on, from list_emails or search_emails. Pass every message you want in ONE call: it costs the user one call instead of one per message. Up to 500 at a time.
forceNoRelease somebody else's claim too. Leave it out unless the user has said to.
mailboxNoIMAP folder the messages are in. Defaults to INBOX.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond annotations: clarifies it moves nothing, marks nothing read, reports unheld messages without error, and precisely defines force's effect. This is rich operational context not in the structured data.

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

Conciseness5/5

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

Four sentences, each front-loaded and dense with necessary information. No wasted words despite the complexity.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers all critical aspects: what it does, when to use it, side effects (none), and edge cases (unheld messages, force). Complete for correct invocation.

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 coverage is 100%, so baseline is 3, but the description adds meaningful semantics for force (clears claims with no recorded holder) and the result naming behavior, elevating it.

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?

States the specific action (releasing claimed messages) and ties it directly to the sibling claim_email. The scope constraint 'only your own claims' further distinguishes this from other claim-related tools.

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

Usage Guidelines4/5

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

Explains when to use it (to let a colleague take claimed messages) and the force behavior, but doesn't explicitly name alternatives like assign_email which might also transfer ownership.

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