Skip to main content
Glama

Poll ZCode session lifecycle events

zcode_session_events
Read-only

Read a bounded page of ZCode session lifecycle events using cursor-based paging from the newest or oldest log, so agents can audit session history and detect gaps.

Instructions

Read a bounded page of existing ZCode JSONL lifecycle events for a session. Pass the returned cursor on subsequent calls. This is not the v4 stream: assistant text and tool arguments/results are unavailable. The first call starts at the newest log by default, or the oldest retained log with start=oldest; gaps report incomplete history, rotation, truncation or unreadable records.

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": {
      "taskId": "<taskId>"
    },
    "name": "zcode_session_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
cursorNo
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds real value on top: bounded paging with cursor continuation, default starting point versus start=oldest, and an explicit warning that gaps mean incomplete history, rotation, truncation, or unreadable records. It stops short of saying whether the page size or total count is returned, but the behavioral profile is substantially richer than the annotations alone.

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 dense sentences with the core action front-loaded and no filler. The final sentence is telegraphic ('gaps report incomplete history, rotation, truncation or unreadable records'), which compresses well but reads as a run-on list rather than clean guidance.

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?

No output schema exists, so the description carries the return-value burden, and it covers paging, cursor return, and gap signaling adequately. What an individual event record contains is left unstated, which is the main remaining gap for a polling tool.

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

Parameters4/5

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, and it does for cursor ('pass the returned cursor on subsequent calls') and start ('start=oldest' vs default newest). limit is only implied by 'bounded page' and taskId is only implied by 'for a session', leaving the numeric bounds and session-id format to the schema.

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: 'Read a bounded page of existing ZCode JSONL lifecycle events for a session.' It also carves out scope by saying 'This is not the v4 stream: assistant text and tool arguments/results are unavailable', so an agent knows exactly what data this does and does not return.

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

Usage Guidelines4/5

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

Gives concrete operational guidance: pass the returned cursor on subsequent calls, and choose between default newest-first versus start=oldest. The negative statement about missing assistant text and tool args steers callers toward content-oriented siblings, though no sibling is named explicitly for that case.

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