Get investigation
refix_get_investigationRead the state of an investigation started with refix_investigate. While it is queued or running, this call waits up to 25 seconds for the state to change or for a new step in progress, so call it again right away until it finishes. The user sees nothing while this runs unless you send it: when a result has new_steps, tell the user in one short plain sentence what Refix is doing before the next call. Use Refix's numbers exactly. Never starts or reruns analysis. When the state is needs_input, ask the user pending_input.question and send their answer with refix_investigate and response_to_input_id. When the answer ends with suggested follow-ups, offer them to the user; send the one they pick with refix_investigate and this session_id.
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": {
"investigation_id": "<investigation_id>"
},
"name": "refix_get_investigation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| investigation_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | ||
| answer | Yes | ||
| question | Yes | ||
| new_steps | Yes | Raw notes on what Refix did since your previous call, oldest first. Empty when nothing is new. Not text for the user: say it in your own words. | |
| error_code | Yes | ||
| report_url | Yes | ||
| session_id | Yes | ||
| next_action | Yes | What to do before the next call, when set. | |
| pending_input | Yes | ||
| investigation_id | Yes |