Retrieve condensed recent events from a Claude Code run to monitor progress, filter by event type, and page through updates by passing the returned next sequence back as since_seq.
Condensed recent events for a run (each ≤300 chars, untrusted). Pass next_seq back as since_seq.
| Name | Required | Description | Default |
|---|---|---|---|
| kinds | No | ||
| run_id | Yes | ||
| max_chars | No | ||
| max_items | No | ||
| since_seq | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral context. It usefully discloses that events are condensed to ≤300 characters, are untrusted, and support pagination via next_seq, but it omits read-only/mutation behavior, ordering, permissions, and other operational traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two tightly written sentences with no wasted words, and the core purpose plus pagination instruction are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists and reduces the need to explain return values, the tool has five parameters, no annotations, and 0% schema description coverage. The description is too thin to fully equip an agent to choose and invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for five undocumented parameters. It clarifies since_seq pagination and implies character truncation, but does not explain run_id, kinds, max_chars, or max_items, leaving most parameters ambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource being returned: condensed recent events for a specific run. It does not name an explicit retrieval verb or distinguish this from siblings like session_result or session_status, but the core purpose is still understandable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only usage instruction is pagination mechanics: 'Pass next_seq back as since_seq.' It does not say when to use this tool versus session_result, session_status, or session_wait, nor does it state any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.