okto-nexus

Overview Schema Source Related Servers Discussions Admin

event_wait

Reads the event log with optional blocking long-poll to wait for new workspace, agent, or handoff events; use a cursor to paginate and timeout_seconds>0 to block until one arrives.

Instructions

Read the event log; optionally long-poll (0/omitted/null = snapshot; >0 blocks). Scoped like event_get (actors outside your comm scope omitted). Patterns: okto-nexus://reference/monitoring.

Input Schema

TableJSON Schema

Name	Required	Description
`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).
`timeout_seconds`	No	Long-poll bound in SECONDS (optional; default 0). 0/omitted/null = an immediate non-blocking snapshot; >0 OPTS IN to a BLOCKING long-poll until an event arrives or the timeout elapses.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.10Sep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does a solid job: it discloses the visibility scoping ("actors outside your comm scope omitted"), the blocking semantics of the timeout, and points to a monitoring reference. It stops short of permissions or rate-limit context, but the key behavioral traits of a long-poll read are surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the primary action and the blocking rule, with no filler. Slightly dense but every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter read tool with an output schema and full schema coverage, the description supplies the missing behavioral context (scoping, blocking, monitoring reference) without needing to explain return values. Adequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all eight parameters are already documented, including the 0/omitted/null snapshot semantics for timeout and the limit/cursor meaning. The description merely restates the timeout rule rather than adding new syntax or format detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read the event log") and disambiguates itself from the sibling event_get by noting the scoping relationship and by being the tool that offers long-polling. An agent can tell what it does, though the distinction from event_get/event_cursor is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The blocking-vs-snapshot behavior is explained, which implies when you'd reach for this tool, but there is no explicit statement of when to prefer it over event_get (plain read) or event_cursor, and no exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.