explain
Shows the evidence behind one recorded mark: the files and patterns searched, how counts were reached, and what was left out, so an agent can verify the finding before acting on it.
Instructions
Returns the evidence behind one mark, computed again: the files and patterns searched, the counts and what was left out.
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": {
"repository": "<repository>",
"mark": "<mark>"
},
"name": "explain"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The revision to compare with: a commit, a tag or a branch. When it is not an ancestor of the head, their merge base is used and the answer says so. Without it, the default base the repository declares in .plimsoll.toml is used. | |
| mark | Yes | The identifier of one mark, as status or report printed it, for example shape.file-size:src/store.ts. | |
| repository | Yes | Absolute path of the repository: its top folder or any folder inside its working tree. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | Yes | ||
| head | Yes | ||
| more | Yes | ||
| marks | Yes | ||
| counts | Yes | ||
| history | Yes | ||
| touched | Yes | ||
| version | Yes | ||
| evidence | No | ||
| question | Yes | ||
| resolved | Yes | ||
| sections | No | ||
| standing | Yes | ||
| detectors | Yes | ||
| footprint | No | ||
| summaries | Yes | ||
| reportOnly | Yes | ||
| notAnalysed | Yes | ||
| acknowledged | No | ||
| acknowledgedIn | No |