Submit feedback to Bucky
submitBuckyFeedbackOpen a human-reviewed feedback form and submit it to the Bucky product team. Call only when the user explicitly asks to send feedback, report a problem, suggest an improvement, or praise something. The server asks the MCP client to show the form; nothing is saved unless the human accepts it. Do not use for silent agent self-reporting.
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": {
"context": "<context>"
},
"name": "submitBuckyFeedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| draft | No | Optional. Feedback you drafted from this chat when the user asked you to: what they tried, what went wrong, what they expected. Plain words. No prompts, raw tool output, addresses, names, personal data or secrets. It fills the form for the user to edit. | |
| confirm | No | Only when this client cannot show the form: call first without confirm to get the draft back, show it to the user, and call again with the same draft and confirm: true only after the user says to send it. | |
| context | Yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details. | |
| submissionId | No | Optional. A UUID for this submission; generated server-side when omitted. Pass the same UUID when retrying this exact feedback so it is not recorded twice. | |
| conversation_id | No | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. | |
| affectedToolName | No | Tool the user is commenting on, when already known |