send_batch
Send an approved batch of formatted messages and files to Telegram topics using a stable request ID to prevent duplicate sends and return recorded receipts.
Instructions
Send an explicitly authorized batch after draft review and structural preview. Use one stable request_id per intended send. Reusing it returns recorded receipts, never resends uncertain/unfinished parts; a different plan with that id is rejected. Inspect complete and every part state: sent, unconfirmed, not_attempted. On error, stop and report exactly what is confirmed. Do not create a new id to retry blindly. All messages share one configured destination. Internal/provenance parts are not client copy. Signature metadata identifies the sending session, not text authorship. Top-level reply_to is a stored inbox key; reply_part selects the root batch part that answers it. Nested part reply_to still names an earlier part. Album parts accept 2–100 files and are split into linked Telegram groups of ten.
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": {
"request_id": "<request_id>",
"project": "<project>",
"subject": "<subject>",
"agent": "<agent>",
"model": "<model>"
},
"name": "send_batch"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | ||
| model | Yes | ||
| parts | No | ||
| route | No | ||
| project | Yes | ||
| subject | Yes | ||
| contents | No | ||
| reply_to | No | ||
| template | No | ||
| reply_part | No | ||
| request_id | Yes |