Rius

List Agent Lifecycle Events

agent_lifecycle_events

Read-only

The lifecycle log of a workspace's agent instances — when each copy started, finished, was lost or recovered — newest first, timed when it happened rather than when a page was loaded.

This is the same read the Rius console's Agent page draws its timeline from. The kinds are the server's: started (first heartbeat), finished (clean-shutdown ping), lost (silent past the gone threshold, timed at the sweep tick that noticed and carrying last_seen_at for the last ping before the silence) and recovered (a ping after lost). stale is a read-time status on list_agents, never an event. open_trace_count and open_traces say what was in flight at a lost or recovered moment.

workspace: optional workspace id, name, or org-name/workspace-name when the same name occurs in two of your orgs (defaults to your default; use list_workspaces to discover them). hours: lookback window in hours (default 24), used for whichever of start/end is not given. start: optional absolute RFC3339 lower bound (e.g. "2026-08-01T00:00:00Z"); overrides the hours-derived value when given. end: optional absolute RFC3339 upper bound; overrides the hours-derived value when given. agent: optional exact agent name; omit for every agent in the workspace. instance: optional exact instance id; composes with agent. limit: max rows (default 50, server max 200). cursor: opaque page token from a previous call's next-page hint, to fetch the page after it.

Example:

When did the planner agent's copies die today?

{ "name": "agent_lifecycle_events", "arguments": { "agent": "planner" } }

Everything that happened to inst-planner-01 this week.

{
    "name": "agent_lifecycle_events",
    "arguments": { "hours": 168, "instance": "inst-planner-01" }
}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	No
`agent`	No
`hours`	No
`limit`	No
`start`	No
`cursor`	No
`instance`	No
`workspace`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: ordering (newest first), event-time vs page-load-time semantics, the meaning of each kind, the timing rule for 'lost' (sweep tick that noticed) plus the last_seen_at caveat, and the provenance note that this is the same read the console timeline uses. It does not cover pagination behavior or row shape, but the annotations already establish the safety profile.

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?

Front-loads purpose, then event semantics, then a per-parameter block, then worked examples — a sensible order. It is long, and the multi-line parenthetical for `lost` is dense, but nearly every sentence adds operational detail rather than padding.

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

Completeness5/5

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

An output schema exists so return values need not be detailed, yet the description still explains the key event payload fields (last_seen_at, open_trace_count, open_traces). For an 8-param read tool with zero schema descriptions, this is complete enough to call correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does so for all 8 parameters: workspace id/name/org-qualified form with default, hours default and its interaction with start/end, RFC3339 format with example values and override precedence, agent exactness, agent+instance composition, limit default and server max (200), and the opaque cursor's origin.

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

Purpose5/5

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

States a specific verb and resource ('lifecycle log of a workspace's agent instances') and enumerates the exact event kinds it returns (started/finished/lost/recovered). It also explicitly distinguishes itself from the sibling list_agents by noting 'stale' is a read-time status there, never an event here.

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

Usage Guidelines5/5

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

Routes the agent to alternatives with conditions: use list_workspaces to discover workspaces, list_agents for current status rather than history. Two concrete example queries ('when did planner's copies die today', 'everything that happened to inst-planner-01 this week') demonstrate when to reach for it.

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

All Rius tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?