submit_feedback
Files a bug report or feature request when the user asks to report something. Confirm the title and body with the user before filing. Passing backtest_id attaches that backtest's spec so the issue can be reproduced.
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": {
"title": "<title>",
"body": "<body>"
},
"name": "submit_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | What was expected, what happened, and any spec involved. Write it from the user's report, not from your own summary of it. | |
| title | Yes | One line naming the problem or request. | |
| category | No | Omit it and it will be inferred from the text. | |
| severity | No | ||
| backtest_id | No | The result this is about, if any. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| status | No | ||
| message | No | ||
| category | No | ||
| severity | No | ||
| feedback_id | No |