Skip to main content
Glama

Read a session part in bounded chunks

zcode_session_part_content
Read-only

Reads base64-encoded chunks of an assistant text or tool snapshot as UTF-8 JSON, using offset/limit paging and expected version checks to resume interrupted reads safely.

Instructions

Read UTF-8 JSON bytes of an assistant text or tool snapshot in base64 chunks. Pass version as expected on subsequent pages; updates normally invalidate the read, but same-millisecond same-size changes may be missed. Content may contain task text, tool arguments and output.

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>",
      "partId": "<partId>"
    },
    "name": "zcode_session_part_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
partIdYes
taskIdYes
expectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses consistency semantics: updates normally invalidate the read but same-millisecond same-size changes may be missed. It also warns that content may contain task text, tool arguments and output, which matters for handling sensitive data. It does not say how the end of content is signalled.

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, front-loaded with what is read and in what encoding. The phrase 'Pass version as expected' is slightly awkward in wording but no sentence is wasted.

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?

With no output schema, the description correctly carries the return format (base64-encoded UTF-8 JSON bytes) and the pagination/version contract. The main remaining gap is termination and chunk-size signaling, which the agent must discover empirically.

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 description coverage is 0% across five parameters including a nested 'expected' object, so the description must compensate. It does explain 'expected' as an optimistic-concurrency version for subsequent pages and hints at offset/limit via 'bounded chunks' and 'pages', but leaves taskId, partId, and limit/offset units and defaults undocumented.

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 UTF-8 JSON bytes of an assistant text or tool snapshot'), and adds the transport format (base64 chunks). It is clearly distinguishable from list-style siblings like zcode_session_parts, though it never names an alternative tool explicitly.

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?

Pagination guidance is given ('Pass version as expected on subsequent pages'), which implies use for reading part bodies. However, there is no explicit when-to-use vs when-not guidance and no statement of prerequisites such as needing a partId from zcode_session_parts first.

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