Revdoku

Mailbox Unlock

mailbox_unlock

Idempotent

Unlock a mailbox locked by this MCP connector.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`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.
`mailbox_id`	Yes	Value for mailbox id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mailbox`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

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

A3.6/5.0

Behavior3/5

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

Annotations already declare the safety profile (write operation, idempotent, non-destructive), so the bar is lower. The description usefully adds the scope constraint that only connector-created locks can be released, but does not cover auth/permission needs or what happens to a lock not owned by this connector.

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?

A single short sentence with zero filler, and the scope-limiting qualifier is included up front rather than buried.

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?

An output schema exists so return values need not be described, and the schema carries the parameter detail. The description covers the essential behavioral constraint (connector-owned locks), leaving only minor gaps such as behavior on an unrecognized or already-unlocked mailbox.

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 fully documents mailbox_id, account_id, and reason, including the caveats about account inference and reason hygiene. The description adds nothing beyond the schema, which is the baseline-3 case.

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

Purpose4/5

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

States a specific verb (unlock) and resource (mailbox), and the qualifier 'locked by this MCP connector' distinguishes it from the file-oriented sibling mailbox_unlock_file. It is clear on its own, though it does not name the sibling explicitly.

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

Usage Guidelines3/5

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

The phrase 'locked by this MCP connector' implies the precondition for use (only locks this connector created can be released), but there is no explicit when-to-use/when-not guidance and no alternatives named among siblings like mailbox_unlock_file or mailbox_lock.

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.