Revdoku

Mailbox File Write

mailbox_file_write

Write a text file to private mailbox storage. Respect locks and expected_mailbox_revision_id. Use direct uploads or the CLI for binary files.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Mailbox-relative path, for example notes.md, leads.csv, or site/index.html.
`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.
`content`	Yes	UTF-8 text file content (HTML/CSS/JS/JSON/SVG/Markdown/etc.). Use revdoku upload or REST direct uploads for binary files (images, fonts, PDFs).
`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.
`content_type`	No	MIME type such as text/html, text/css, text/plain, or application/json.
`expected_mailbox_revision_id`	No	Optional optimistic-concurrency token from mailbox.current_mailbox_revision_id. A stale value returns MAILBOX_REVISION_CONFLICT without saving.

Output Schema

TableJSON Schema

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

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

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds meaningful behavior beyond them: writes are lock-aware and honor the revision token, and it flags the binary-file limitation, giving useful operational context.

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?

Three short, front-loaded sentences with zero filler; the core action leads and the constraints follow.

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 full schema coverage, an output schema, and annotations, the description covers the key behavioral points an agent needs (lock and revision awareness, text-only scope). Only the overwrite/non-idempotent consequence of re-writing an existing path 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 itself documents all 7 parameters including the revision-conflict behavior. The description only re-emphasizes the revision/lock interaction and adds no syntax or format detail the schema lacks, so this is the baseline 3.

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 and resource (write a text file to mailbox storage) and scopes it to text files, distinguishing it from binary-upload paths. It does not explicitly name sibling tools like mailbox_file_write_many or mailbox_file_append_text, so an agent must infer the boundary from the name alone.

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 clear context ('Respect locks and expected_mailbox_revision_id') and an exclusion (use direct uploads or the CLI for binary files). It stops short of routing between write_many/append_text alternatives, which would be needed for a 5.

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.