Investigate
refix_investigateStart a new Refix investigation, or answer a pending clarification with response_to_input_id, or dig into a finding from refix_list_findings with finding_id. Send at most one of session_id, response_to_input_id or finding_id. Counts toward the workspace's Refix usage. For a follow-up about an earlier Refix answer in this chat, pass that answer's session_id so Refix keeps the context. If the question names a tool that is not in usable_sources from refix_get_context, tell the user it is not connected and ask whether to check the connected sources before starting. Give the user report_url at once: it opens this conversation in Refix. Then call refix_get_investigation for the result; do not start another investigation to check progress.
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": {
"question": "<question>",
"idempotency_key": "<idempotency_key>"
},
"name": "refix_investigate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | The user's question. With response_to_input_id, the user's answer to Refix's pending question instead. | |
| finding_id | No | Ask about one update: finding_id from refix_list_findings. | |
| session_id | No | Continue a finished conversation: session_id from an earlier investigation. | |
| idempotency_key | Yes | A new random value, such as a UUID, for each new request. Reuse it only to retry the exact same request. | |
| response_to_input_id | No | Answer Refix's pending question: pending_input.input_id from refix_get_investigation. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | ||
| report_url | Yes | ||
| session_id | Yes | ||
| investigation_id | Yes |