Skip to main content
Glama

Read a bounded ZCode session snapshot

zcode_session_parts
Read-only

Read paginated assistant text and tool part snapshots from ZCode's SQLite database to inspect stored session history; content is hidden by default and can be included per page.

Instructions

Read a page of assistant text and tool part snapshots from ZCode's SQLite database. This is not a live event stream: parts can change and pagination cannot detect changes to earlier rows. Content is omitted by default; opting in may expose task text, tool arguments and results. Parts above 8192 bytes are omitted, and the cursor sorts by ID, not chronological order.

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_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonextAfter from the previous page, or omit to start.
limitNo
taskIdYes
includeContentNoInclude small part content; default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint supplied, the description carries real behavioral weight: snapshot-vs-live semantics, stale-page risk during pagination, default content omission with a privacy warning about task text/tool arguments/results, and an 8192-byte size cutoff. It also discloses the non-obvious cursor ordering (by ID, not chronological), which materially changes how an agent paginates.

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

Conciseness5/5

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

Four dense sentences with no filler, front-loaded with purpose followed by the not-live caveat, privacy note, and truncation rule in descending order of importance. Every sentence adds a decision-relevant fact.

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 a read-only, four-parameter tool with no output schema, the description covers the key risks (staleness, content exposure, truncation, cursor ordering). It leaves unspecified what a 'part' record structurally contains and whether a limit default exists, minor gaps for a snapshot reader.

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 coverage is 50%, so the description must compensate and largely does: it explains what includeContent turns on and the exposure risk, and clarifies that the 'after' cursor advances by ID rather than time. It does not address the limit bounds or the taskId pattern, which remain schema-only, but the two least obvious parameters gain real meaning.

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 ('Read a page') and resource ('assistant text and tool part snapshots from ZCode's SQLite database'), and the clarification 'This is not a live event stream' implicitly separates it from an event-streaming sibling. It stops short of naming the alternative tool (e.g. zcode_session_part_content) for full content retrieval, so the differentiation is implied rather than explicit.

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?

Gives useful in-tool guidance: content is off by default, opting in exposes sensitive text, and pagination won't reflect later changes to earlier rows. However, it never states when to choose this over zcode_session_part_content or zcode_session_events, nor any prerequisites, leaving alternative selection to inference.

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