Skip to main content
Glama

get

Read a session's turns as written, including reassembled blocks, and expand a search hit into surrounding context by specifying the turn range to inspect.

Instructions

Read one session's turns as they were written — whole blocks, splits reassembled, nothing ranked or summarized. Typically the follow-up to a search verb: expand a result into the turns around it. Sessions run to thousands of turns: read the stretch you need, not the session.

Input Schema

NameRequiredDescriptionDefault
toNoLast turn to read, as the session's own seq. Omit it to read a fixed span from `from`; every reply names the range it covered.
fromNoFirst turn to read, as the session's own seq, which a hit's `→ get` line gives you. Defaults to the session's start.
memoryNoMemory to read for this call, as it stands — the one the hit's `→ get` line carries, and none when it carries none, so the drill-down reads what the search read. Omitted, the server's memory, where a session this host has not finished pushing is read from the local memory.
session_idYesSession id from a recall hit's `→ get` line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A3.8/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 non-obvious traits: content is returned as written, splits are reassembled, and nothing is ranked or summarized. However, it says nothing about cost/latency on huge sessions, error behavior for missing sessions, or the read-only guarantee beyond the verb 'Read'.

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?

Three tight sentences, front-loaded with what the tool returns, then when to use it, then a scoping warning. No redundant restatement of the name or schema.

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 tool with complete schema coverage and no output schema, the description covers data fidelity, scoping, and the search-to-get workflow. Return structure is only partially sketched (whole blocks, named ranges), which is a minor gap.

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 coverage is 100%, so the schema already documents session_id, from, to, and memory in detail. The description reinforces range-scoped reading ('read the stretch you need') but adds no per-parameter meaning beyond what the schema states.

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?

The description states a specific action — reading one session's turns verbatim, with splits reassembled and no ranking or summary — which separates it from the search-oriented siblings (recall, scan). The generic name 'get' is compensated by this textual specificity, though it does not name the exact sibling it follows up on.

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?

'Typically the follow-up to a search verb: expand a result into the turns around it' gives a clear when-to-use context, and 'read the stretch you need, not the session' sets a scoping constraint for large sessions. It stops short of explicitly naming recall/scan as the alternative or stating when-not-to-use.

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

Deploy Server

Other Tools