Skip to main content
Glama
Sign In
session-recall

session-recall

by AbsoluteMode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

step

Navigate to the next or previous turn within a session transcript to review adjacent context.

Instructions

Walk to an adjacent turn ('next' or 'prev').

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>",
      "uuid": "<uuid>",
      "direction": "<direction>"
    },
    "name": "step"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
countNo
directionYes
session_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description is the sole source of behavioral info. It only mentions the basic action without discussing side effects, permissions, rate limits, or the effect of the 'count' parameter. The tool's behavior beyond a single step is opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but does not front-load critical parameter info. It could be equally concise yet more informative by adding parameter hints.

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

Completeness2/5

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

Given 4 parameters (3 required) and an output schema, the description is insufficient. It does not explain how sessions, UUIDs, or counts relate to walking, nor what the tool returns. This makes it hard for an AI agent to use correctly without additional context.

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

Parameters1/5

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

Schema coverage is 0%, so the description must compensate, but it only mentions 'direction' ('next' or 'prev'). It does not explain 'uuid', 'session_id', or 'count' (with default 1). Users are left guessing the meaning and purpose of these parameters.

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 clearly states the verb 'Walk' and the resource 'adjacent turn', with acceptable direction values 'next' or 'prev'. It is specific enough to distinguish from sibling tools like expand_around, grep, recall_search, recent_sessions, which are not navigation-focused.

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?

No guidance is provided on when to use this tool versus alternatives, or any prerequisites. The description lacks context on when stepping makes sense or when other tools might be more appropriate.

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