Revdoku

Mailbox Create

mailbox_create

Create an email mailbox with optional file storage. Free uses username as a dot-separated prefix with a permanent 12-character random suffix; paid plans can choose an exact username. Omit username to generate an address. Taken exact names return EMAIL_ALREADY_EXISTS. Reserved shared-domain words return EMAIL_NAME_RESERVED with custom-domain guidance. Returns email.address after receiving is confirmed.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	No	Built-in domain such as revdokumail.com on any plan, or a ready custom email domain owned by the selected account on an eligible plan. Omit for the default platform domain.
`reason`	No	Optional reason for this action. AI agents should include a short purpose for intentional reads and changes when known. Do not invent a reason or include secrets, file contents, or transcripts.
`metadata`	No	Optional JSON metadata object stored with the mailbox.
`username`	No	Free: prefix for a generated address. Paid: exact name before @. Omit to generate one; empty names are invalid.
`account_id`	No	Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a mailbox id.
`description`	No	Optional human-readable description for the mailbox.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mailbox`	Yes
`guidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / username / description

Previous value: -"Email name before @. Omit to generate one; empty names are invalid."New value: +"Free: prefix for a generated address. Paid: exact name before @. Omit to generate one; empty names are invalid."

Changed3 schema fields changedOct 5, 2026

removedInput schema / properties / title

Removed value: -{
-  "description": "Human-readable title for the mailbox.",
-  "type": "string"
-}

changedOutput schema / properties / mailbox / properties / email / description

Previous value: -"Accepted email activity. Creation and write-authorized include_email reads also return the full address and receiving state. Activity is not a delivery cursor. Use mailbox_email_list to poll for arrivals."New value: +"Email activity and the address permitted by the connection. Creation and write-authorized include_email reads also return receiving settings. Activity is not a delivery cursor. Use mailbox_email_list to poll for arrivals."

removedOutput schema / properties / mailbox / properties / title
```
Removed value: -{
-  "type": "string"
-}
```

AddedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent. The description adds real behavioral context beyond them: suffix generation for free plans, the EMAIL_ALREADY_EXISTS and EMAIL_NAME_RESERVED failure modes with custom-domain guidance, and the fact that the address is only returned after receiving is confirmed. It does not cover auth/authorization specifics, which the schema partly handles.

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?

Front-loaded with the core action, then dense but purposeful sentences covering plan differences, error codes, and return timing. Every sentence carries information, though the density is high and could be slightly tighter.

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?

With an output schema present, return values need not be explained, yet the description usefully notes email.address availability gating. Given six params with full schema coverage and a nested metadata object, the description covers the creation flow and failure modes adequately; only auth/rate-limit nuance is left implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters (username plan semantics, domain defaults, account_id authorization, reason guidance). The description reinforces the username/domain behavior and ties parameters to error outcomes, but adds little syntax or format detail beyond the structured fields, so the baseline 3 applies.

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 a specific verb and resource ("Create an email mailbox") plus the optional storage capability, and is clearly distinct from siblings like mailbox_update, mailbox_list, or mailbox_delete_permanently. An agent can identify the operation without opening the schema.

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?

Gives concrete conditional guidance: free vs paid username behavior, omit username to auto-generate, and the domain default. It does not explicitly route away from alternatives (e.g., 'use mailbox_update to change an existing mailbox'), so it stops short of the top band.

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

All Revdoku tools Inspect

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.