Record an investigation
webops_record_investigationRecords one investigation in the website's log: the question, its kind, the playbook and version, tools called, outcome and what was missing. Feeds new playbooks and data sources. Changes no website data. Nothing happens until the person confirms: this returns a summary and a code for tc_confirm.
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": {
"domain": "<domain>",
"question": "<question>",
"kind": "<kind>",
"playbook": "<playbook>",
"tools": "<tools>",
"outcome": "<outcome>",
"missing": "<missing>"
},
"name": "webops_record_investigation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | The kind of question in a few words. | |
| tools | Yes | The tools called, comma-separated (may be empty). | |
| domain | Yes | ||
| missing | Yes | What data would have answered it (empty when nothing was missing; required for cannot_tell). | |
| outcome | Yes | answered, cannot_tell or nothing_happened. | |
| playbook | Yes | The playbook followed, P0–P6. | |
| question | Yes | The question as the person asked it (at most 512 characters). |