get_events
Read the daemon's durable feed of autonomous transitions to audit what just happened or replay events forward from a known ID.
Instructions
Use when: you need the daemon's own account of what it just did.
The durable feed of autonomous transitions (``service.failed``,
``service.degraded``, ``service.deploy_succeeded``, ``model.ready``,
...), readable by any authenticated token. Two directions, and picking
the wrong one walks the wrong way through history.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_events"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows in one page, clamped to [1, 200] here and server-side; omit for 50. | |
| types | No | Comma-separated event types to keep (e.g. ``service.failed,model.ready``); only the first 10 entries are honoured. Omit for every type. | |
| cursor | No | Browse **backwards** from here (id DESC, newest first): pass the previous page's ``next_cursor`` to see what just happened. Omit for the newest page; passing it together with ``since_id`` is a 400. | |
| service | No | Keep only events for this exact service name; omit for every service. | |
| since_id | No | Replay **forwards** from this event id (id ASC, rows with id > it) — the resume mode after processing up to that id. Omit to browse backwards instead; passing it together with ``cursor`` is a 400. To keep replaying forward, pass the page's ``next_cursor`` back as ``since_id``, never as ``cursor``. |