Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

restore_snapshot

Destructive

Revert to a saved pre-edit version when the current hash still matches the snapshot; local approval is required.

Instructions

Restore a saved pre-edit version if the current hash still matches the snapshot. Requires local approval.

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": {
      "snapshotId": "<snapshotId>"
    },
    "name": "restore_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshotIdYesSnapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds two non-obvious behaviors the annotations cannot convey: the restore is conditional on the hash matching, and the call requires local approval, both of which affect whether an agent should attempt it.

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 short sentences with the operation first and the two critical constraints (hash match, approval) immediately after. Nothing is redundant or padded.

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 destructive single-parameter tool, the description covers the key precondition and approval gate, and no output schema exists so return values are unaddressed. It is silent on what happens when the hash does not match (error vs. no-op) and on exactly what state is overwritten, which are material gaps for a destructive operation.

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 coverage is 100% for the single snapshotId parameter, so the schema does the documenting. The description adds no meaning about the ID's format or where to obtain it, which is the baseline 3 case when the schema is fully covered.

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 and resource (restore a saved pre-edit version) plus the exact condition under which it applies. It does not name a sibling to distinguish itself from, but the conditional framing makes the operation recognizable without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'pre-edit version' suggests undoing edits, and 'if the current hash still matches' signals the applicability check. There is no explicit when-not case or pointer to a related tool for inspecting snapshots or hash state.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.