Skip to main content
Glama
Sign In
Longhand

Longhand

by Wynelson94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_file_history

Retrieve the complete chronological history of edits for any file across all sessions. Optionally filter by a specific session.

Instructions

Get every edit ever made to a file across all sessions, chronologically.

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

Input Schema

NameRequiredDescriptionDefault
file_pathYes
session_idNoOptional: limit to a single session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Description implies read-only, chronological retrieval. No annotations, so description carries burden. It does not mention potential size limits, error behavior, or authorization needs.

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?

Single sentence, front-loaded with action and scope. No redundant words.

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?

Indicates output is a chronological list of edits, but lacks details on output structure (fields like timestamp, user, change type). No output schema to compensate.

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 covers session_id with description, but file_path lacks description. The description does not add meaning for file_path beyond its name, and session_id context is already in schema.

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 'get every edit ever made to a file', specifying verb and resource with scope (all sessions, chronological). Distinguishes from siblings like get_session_timeline or replay_file.

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 vs alternatives. Siblings include get_session_timeline and get_episode, but no context for choosing between them.

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