Revdoku

Mailbox File Append Text

mailbox_file_append_text

Append UTF-8 text to an existing private Revdoku mailbox file, such as txt, md, csv, jsonl, js/code files, and similar text formats. This is not a binary-file API and it does not parse CSV or JSON; for ordinary .json, raw append can make invalid JSON. If the file or mailbox is locked, retry briefly; if it remains locked, report error.details including the lock owner and message.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Existing mailbox-relative text file path, for example leads.csv, notes.md, or src/app.js.
`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 to append. Include any trailing newline wanted after the appended block.
`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.
`newline_before`	No	When true, insert one newline before content only if the existing file is non-empty and does not already end with \n. Defaults to true.
`expected_mailbox_revision_id`	No	Optional optimistic-concurrency token from mailbox.current_mailbox_revision_id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mailbox`	Yes
`appended`	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.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, idempotent=false, destructive=false), and the description adds real value beyond them: text-only scope, no parsing of structured formats, the JSON-corruption hazard, and cooperative lock failure handling with error.details. It does not describe concurrency semantics of expected_mailbox_revision_id, but the operational behavior is well disclosed.

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 tight sentences, each carrying distinct information (what it does, what it is not, failure handling), with the core action front-loaded. No filler.

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?

An output schema exists so return values needn't be explained. The description covers the critical caveats (text-only, format safety, locking) for a mutating write tool, giving an agent everything needed to call it correctly.

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 coverage is 100%, so the schema already documents all seven parameters, including the newline_before default and the revision token. The description adds only indirect semantics (content is UTF-8, append semantics) and no per-parameter detail beyond the schema, so 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 ('Append') plus resource ('UTF-8 text to an existing private Revdoku mailbox file') and enumerates supported formats. An agent can distinguish this append operation from write/copy siblings without opening any 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?

Clearly bounds the tool with negative guidance ('not a binary-file API,' 'does not parse CSV or JSON') and warns that raw append to .json can break it, plus lock-retry behavior. It stops short of explicitly contrasting with mailbox_file_write, which is the nearest alternative for the same resource.

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.