add_evidence_file
Save log files, command output, or configs as case evidence by path; the server reads the file directly, avoiding retyping its contents.
Instructions
Store a file's contents as evidence, read directly by the server (no need to repeat the text). Use for log files, command output saved to a file, configs. A document you keep rewriting (Q&A notes, analysis, design .md) is not evidence: reference its path instead, and when the engineer adds to it, add_evidence only the new part, verbatim — never store the whole file again. Absolute or ~ path. Not available over the remote door (chat clients) — use add_evidence.
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": {
"case_id": "<case_id>",
"path": "<path>"
},
"name": "add_evidence_file"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| case_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |