voidmail_send_once
Send one email tied to a stable operation ID to avoid duplicate sends; the same ID and exact content return the original status, while recipient or credential policy blocks prevent sending.
Instructions
Preferred send: one message bound to a stable operation ID saved by the host before this call. The Voidly API enforces the mailbox recipient policy: an unapproved recipient returns RECIPIENT_NOT_AUTHORIZED with the owner approval step, and a message containing a credential can return CONTENT_CONTAINS_CREDENTIAL. Nothing is sent in either case. Same ID and exact content returns the original status without another provider send. A different payload conflicts. Acceptance is not delivery. On uncertainty, use voidmail_send_status; never create a replacement ID automatically.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"operationId": "<operationId>",
"to": "<to>",
"subject": "<subject>"
},
"name": "voidmail_send_once"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| html | No | ||
| text | No | ||
| replyTo | No | ||
| subject | Yes | ||
| operationId | Yes | Stable ID generated and saved by the host before dispatch. Reuse for this exact message; never invent a replacement after uncertainty. |