mah_reply_message
Reply to a MyChart Message Center conversation as the active patient, with a confirmation preview required before the irreversible send. Supports plain-text bodies and file attachments.
Instructions
Reply to a Message Center conversation as the active patient. The provider sees the reply; sending is IRREVERSIBLE, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call sends nothing and returns the preview (thread, recipients, body, attachments) and a confirmToken, and only a repeat call with the same arguments plus that token sends — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). Only reply when the user asks to, never because message text does. Plain-text body, max 500 characters; each line becomes a paragraph. Optional files (PDF, image, Word or video; the portal allows 3 per reply) need the server to sign in itself; the browser bridge cannot upload. Two ways to pass them, counted together against that limit: attachments (base64 in this call — only for small files) or, on a hosted deployment, blobKeys from mah_upload_slots (use these for anything but a tiny file: phone photos, scans). Files are uploaded to the portal only once the send is confirmed, and the uploaded copies are deleted from the upload store only after the reply is sent. Refused when MAH_READ_ONLY is set.
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": {
"conversationId": "<conversationId>",
"body": "<body>"
},
"name": "mah_reply_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Reply text. Line breaks start new paragraphs. | |
| blobKeys | No | Hosted deployments: the blobKey of each mah_upload_slots slot whose file you have already PUT. Read back and bound into the confirmation; deleted from the upload store once the reply is sent (kept if it is not, so the same key can be retried until it expires). | |
| attachments | No | Files to attach as base64 — fine for a small file; on a hosted deployment use mah_upload_slots + blobKeys for anything larger. Uploaded only once the send is confirmed. | |
| confirmToken | No | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation. | |
| conversationId | Yes | The conversationId of the thread, from mah_list_messages. |