send_feedback
Opens a feedback card for the user to review, edit, and send themselves; use it to report missing capabilities or frustration without sending or attaching anything automatically.
Instructions
Open the Brilliant feedback card for the user to review and send. This does NOT send: the card opens, the user presses Send, and you tell them it is open and waiting (never claim it was sent). message is OPTIONAL (pre-fill a draft or open empty); attachments is tolerated but ignored (nothing about the user's world is ever attached). Feedback is a routing decision, not one surface, and consent scales with what leaves the machine: the user's words move by the user's act, the user's context moves only per-item opt-in, and your own observations ride telemetry, never GitHub or email. Offer it proactively, once and calmly (at most once per session AND once per class), when you hit a wall or a missing capability, when the user asks for something the product cannot do, or when the user is frustrated. Before running the routing flow (card vs GitHub issue vs email vs Discord), load the full playbook with get_knowledge(["reference/feedback"]).
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "send_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | OPTIONAL. The drafted feedback message, in the user's own framing (the user can edit it before sending). Omit to open an empty card. | |
| attachments | No | Ignored in this version; accepted for backward compatibility (nothing about the user's world is ever attached). |