Get AI conditions
get_ai_conditionsRead what Ankra's AI keeps seeing and how it acts on it. report picks it: conditions (each recurring problem on a subject: occurrences, tickets filed, whether it is chronic; the twin of ankra ai conditions list), condition (one condition's timeline of tickets, probes and playbook runs; needs condition_id; the twin of ankra ai conditions get), playbooks (the steps the AI runs for a kind of condition, adopted or offered as Ankra's templates) or handoffs (platform alerts passed to engineering, with status open, filed or resolved). Needs the organisation's AI experience. A caller confined to one project reads only its conditions and is refused the other three reports. Read-only: adopting or retiring a playbook and acknowledging a handoff are an administrator's acts, not offered here.
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": {
"report": "<report>"
},
"name": "get_ai_conditions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | conditions: rows to return, 1 to 500 (default 100). | |
| report | Yes | Which listing to read. | |
| status | No | handoffs: a comma-separated list of open, filed and resolved (default all). | |
| chronic | No | conditions: only the chronic ones. | |
| condition_id | No | condition: the condition (UUID). |