Skip to main content
Glama
Sign In
transcript-search

transcript-search

by ttrine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_session_context

Retrieve full context from a Claude Code session by session ID. Use it after finding a relevant result to get more context, with an optional message limit.

Instructions

Retrieve full context from a specific Claude Code session. Use this after finding a relevant result to get more context from that session.

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": "get_session_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of messages to return (default: 50)
session_idYesThe session ID to retrieve context from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'retrieve full context' without disclosing what that context includes, the return structure, pagination behavior, or any operational side effects. For a tool with no annotation coverage, this is a significant gap.

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?

Two concise sentences, with the primary purpose front-loaded and the usage guidance following. There is slight redundancy between 'retrieve full context' and 'get more context from that session,' but the overall structure is efficient.

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 2-parameter tool, the description covers the core use case and when to call it. However, it leaves gaps: what 'full context' means, how to obtain the session_id, and what the response looks like. Acceptable but not rich enough for a tool with no annotations or output schema.

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 100%, so both session_id and limit are already documented. The description adds no parameter-level detail beyond reinforcing that session_id identifies the target session, so the baseline of 3 applies.

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 verb ('Retrieve') and resource ('full context from a specific Claude Code session'). It also implies a distinction from the sibling tool by positioning itself as a follow-up to finding a relevant result, though it does not explicitly name the sibling.

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?

The second sentence explicitly tells the agent when to use this tool: after finding a relevant result, to get more context from that session. This provides clear usage context, though it does not name the alternative search tool or describe exclusion conditions.

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