Skip to main content
Glama

get_turn

Retrieves a single full, unedited conversation turn by its exact ID so you can verify source anchors, terminal outputs, code snippets, and error tracebacks with zero detail loss.

Instructions

Retrieves a single uncompressed, un-summarized conversation turn by its exact ID (Tier 4).

This is the core of Project-M's Lossless Provenance Engine. When an ADR or task references a source anchor (e.g., 'turn:antigravity:caa4cbcc:447'), call this tool to retrieve the 100% complete, unedited historical message.

Guarantees:

  • Zero detail loss: Full terminal outputs, code snippets, and error tracebacks.

  • Zero hallucination: Exact raw payload as ingested from the local client transcript.

Args: turn_id: Deterministic turn identifier (e.g., 'antigravity:caa4cbcc:447' or 'codex:msg-982').

Returns: dict[str, Any]: Complete turn record with source, role, timestamp, and uncompressed content. str: Not-found message if the ID does not exist in the database.

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": {
      "turn_id": "<turn_id>"
    },
    "name": "get_turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
turn_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and mostly succeeds: it declares the guarantee of raw, unedited payload ('zero detail loss', 'zero hallucination') and discloses the failure mode (a not-found message string rather than a record). It does not mention permissions or any access constraints, but for a read-only single-record fetch the behavioral picture is largely complete.

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?

The purpose is front-loaded in the first sentence and the ID example plus return shape are easy to scan. Some padding exists — the 'core of Project-M's Lossless Provenance Engine' framing and the near-duplicate 'zero detail loss' / '100% complete, unedited' claims restate the same guarantee.

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 single-parameter lookup with an output schema, the description covers trigger, input format, content guarantees, and the not-found case. It is complete enough to call correctly; only the absence of guidance on sourcing/validating IDs and any access constraints keeps it from the top mark.

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 0% — the schema only says 'Turn Id' — so the description must compensate, and it does by supplying concrete ID formats ('antigravity:caa4cbcc:447' or 'codex:msg-982') and stating the ID is deterministic and must be exact. This is real meaning beyond the schema, though it does not say where an agent obtains valid IDs beyond ADR/task anchors.

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?

The description names a specific verb and resource ('Retrieves a single uncompressed, un-summarized conversation turn by its exact ID') and scopes it to exact-ID lookup, which clearly separates it from the sibling search_historical_context. An agent can decide between this and a search tool without opening either schema.

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?

It gives a concrete trigger: call this when an ADR or task references a source anchor such as 'turn:antigravity:caa4cbcc:447'. The 'exact ID' framing implicitly routes fuzzy lookups elsewhere, but there is no explicit when-not statement naming the search-based alternative.

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