Label a finding
scout_feedbackRecord a person's verdict on a finding as "not-a-bug" or "confirmed" with their own reason, so triage keeps their answer while the finding stays open and mergeable.
Instructions
Record the person's own verdict on a finding: "not-a-bug" or "confirmed", with their reason if they gave one (at most 300 characters). Call it only with what the person said; never label a finding yourself. The finding is kept either way, keeps its id, and a later filing of the same problem still merges into it; cards and the status pane list a not-a-bug one apart. export: true instead lists every label in the project as candidates for a maintainer to review: they never change an answer key or the dedup by themselves. Touches no browser.
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": "scout_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The finding the person is labelling. Required unless export | |
| export | No | List every label as candidates for a maintainer, instead of labelling | |
| reason | No | Why, in the person's words | |
| verdict | No | "not-a-bug" or "confirmed". Required unless export |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| verdict | No | ||
| findingId | No | ||
| candidates | No |