Send chat message
send_chat_messageWrite a message in a chat, as yourself — as the screen sends it: the chat's people see it at once, and it is told by push and by letter to whoever it calls: in a direct chat the other person, in a group or a project's chat only who it mentions ([~username], the handle list_users gives) or answers (replyTo). An agent of the chat answers when mentioned ([~agent:product]) or replied to, and in a chat with an agent every message is a question to it. A project's chat takes a message from whoever may comment in the project. Answers with 'notified' (who this actually tells, and why: direct, mention, reply — never yourself), 'unresolvedMentions' (what looked like a mention and told nobody, with a reason: unknown, inactive, self, not_in_chat, or an agent's) and 'agents' (the agents it called and their requests). A wrong handle is kept as written and never refused, so that list is the only sign it did not land. With 'quote' (and replyTo), it answers those words of the message: they are kept with yours as quoted, and the message's author is told as for any reply. Text only — files are sent from the screen.
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": {
"chatId": "<chatId>",
"body": "<body>"
},
"name": "send_chat_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The message, Markdown — with $…$ formulas and [~username] mentions. At most 32 KB. | |
| quote | No | Some words of the replyTo message this one quotes, exactly as they read there — shown above your message, linked to them. Needs replyTo; at most 2000 characters. Omit to answer the whole message. | |
| chatId | Yes | The chat's id, as list_chats gives it. | |
| replyTo | No | The message of this chat this one answers. |