Skip to main content
Glama

context_read_session

Read a bounded text transcript for a specific allowlisted Codex session ID to retrieve safe, read-only context with a character limit.

Instructions

Read a bounded textual transcript for an allowlisted UUID-like Codex session ID.

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": {
      "session_id": "<session_id>"
    },
    "name": "context_read_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two real behavioral traits: output is 'bounded' (truncated) and only allowlisted session IDs are accepted. It omits what happens for a non-allowlisted ID (error vs. empty), how truncation interacts with the character budget, and what the transcript looks like.

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?

A single front-loaded sentence with no filler, and the key constraints (bounded, allowlisted, UUID-like) are packed in efficiently. It is terse to the point of leaving the max_chars behavior unaddressed, but nothing is wasted.

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

Completeness3/5

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

For a simple two-parameter read tool with no output schema and no annotations, the description covers identity and access constraints adequately. The major remaining hole is the unmentioned character-budget parameter, which is the only lever controlling output size.

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

Parameters2/5

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

Schema coverage is 0% across 2 parameters, so the description must compensate. It adds meaningful constraint for session_id ('allowlisted', 'UUID-like') that the schema lacks, but says nothing about max_chars — its default of 12000 and how it truncates the transcript go entirely unexplained.

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') and resource ('bounded textual transcript') scoped to a 'Codex session ID', which is enough to distinguish it from a search or listing tool. It stops short of explicitly contrasting itself with context_recent or context_search, so it is clear but not sibling-differentiating.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no when-not-to-use, and no named alternative. The word 'allowlisted' hints at a precondition, but an agent must infer from the sibling names whether to read a session or list/search instead.

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