Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

list_snapshots

Read-only

List available undo snapshots for file changes so you can review or revert workspace edits. Optionally filter by file path and set a maximum count.

Instructions

See available undo snapshots for file changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoOptional file path
limitNoMax snapshots 1..100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds only that these snapshots are 'undo' snapshots tied to file changes; it says nothing about ordering, whether snapshots span all files, or how the results can subsequently be applied.

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

Conciseness4/5

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

A single short sentence with no filler, and the resource is front-loaded. It borders on under-specification rather than verbosity, but nothing is wasted.

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?

With two optional params, no output schema, and annotations covering safety, the description is adequate but incomplete: it never indicates what a snapshot entry contains (identifiers, timestamps) or how to act on one, which matters because no output schema exists to fill that gap.

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 description coverage is 100% – the 'file' and 'limit' params are already documented with type, default, and range in the schema. The description adds no filtering semantics (e.g., scope of 'file', ordering of results) beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('undo snapshots for file changes') but the verb 'See' is weak and it never clarifies that this is a list operation or how it differs from the similarly-named checkpoint_list sibling. An agent can guess the purpose, but not with the precision a 4 or 5 requires.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool (such as checkpoint_list or the restore/edit tools) is named as the next or better step. Usage is only implied by the phrase 'for file changes'.

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