Skip to main content
Glama
Sign In
largefile

largefile

by peteretelej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

revert_edit

Destructive

Restore a file to a previous state after unwanted edits using automatic backups. Reverts to the most recent backup or a specified backup ID, saving current state as a new backup.

Instructions

Restore a file to a previous state from automatic backups.

Use when edit_content made unwanted changes. Backups are created
automatically before each edit. Current state is saved as new backup
before reverting (so revert is reversible). Without backup_id, reverts to
most recent backup. Returns list of available backups with timestamps.

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": {
      "absolute_file_path": "<absolute_file_path>"
    },
    "name": "revert_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
absolute_file_pathYesAbsolute path to the file to revert
backup_idNoBackup ID from response. Omit to use most recent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate destructive and not read-only. Description adds that current state is saved before reverting (making revert reversible) and returns a list of backups. No contradiction with annotations.

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?

Concise 5-sentence description, front-loaded with purpose, no redundant information.

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

Completeness5/5

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

Given no output schema, the description explains return behavior (list of backups with timestamps) and covers all relevant behavioral aspects for a revert operation.

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 100% with clear parameter descriptions. The description adds value by explaining how to omit backup_id to use most recent and that the response includes backup list, going beyond 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?

The description clearly states the verb 'restore' and resource 'file from automatic backups', with sufficient scope to distinguish it from sibling tools like edit_content.

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?

Provides explicit context: 'Use when edit_content made unwanted changes'. Also explains backup creation and default behavior, but does not explicitly mention when not to use or alternative tools.

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