Skip to main content
Glama
Sign In
Longhand

Longhand

by Wynelson94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

replay_file

Reconstruct the state of a file at a specific point in a past Claude Code session by replaying every edit exactly as recorded.

Instructions

Reconstruct the state of a file at a point in a past Claude Code session. Applies every edit verbatim from the session JSONL — no summarization.

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>",
      "file_path": "<file_path>"
    },
    "name": "replay_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
session_idYes
at_event_idNoOptional: reconstruct up to this event

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. It mentions 'no summarization' but fails to disclose whether reconstruction is destructive, idempotent, or requires permissions. Ambiguous if it modifies state or just returns data.

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?

Two concise sentences with no filler. Front-loaded with clear purpose and unique behavior (verbatim edits).

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 no output schema and 3 parameters, description lacks details on return format, side effects, or error conditions. Incomplete for an agent to confidently invoke without additional context.

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 only 33% (only at_event_id described). Description does not explain session_id or file_path beyond their existence, missing opportunity to clarify usage or format.

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?

Clearly states the tool reconstructs a file state at a past session point, with specific verb 'reconstruct' and resource 'file state'. The addition of 'Applies every edit verbatim' distinguishes it from summarization tools like get_file_history.

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 on when to use this tool versus siblings like get_file_history or search. Lacks context for when reconstruction is appropriate or alternative approaches.

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