event_get
Read a cursor-paginated page of the event log to track workspace, agent, and handoff events, with filters for type, agent, task, or trace.
Instructions
Read a cursor-paginated page of the event log (non-blocking). Actors outside your comm scope are omitted; yours and system events always show. Docs: okto-nexus://reference/tool-docs/events.
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": {
"project_root": "<project_root>",
"agent_id": "<agent_id>",
"stream": "<stream>"
},
"name": "event_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max events per page (optional; default 100, clamped to the server maximum, default 1000). | |
| cursor | No | Pagination cursor: the last event_id you consumed; returns event_id > cursor (optional; omit/0 = from the beginning). | |
| stream | Yes | Event stream to read - one of: workspace, agent, handoff. message.created, the message.delivered/message.read receipts and artifact.created are on workspace. | |
| filters | No | Equality filters, AND-combined (optional). Keys: type, agent_id, task_id, handoff_id, trace_id. e.g. {"type":"message.created"}. | |
| profile | No | Response size profile - one of: default, summary, full (optional; summary trims per-call tokens). | |
| agent_id | Yes | Your agent_id; scopes per-event visibility (you only see events you may see). | |
| project_root | Yes | Absolute path to the project (defines the workspace scope). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||