Skip to main content
Glama

snapshot

Create, list, diff, restore, and delete folder undo points with deduplication, .git/node_modules exclusion, dry-run restore, and alternate restore paths.

Instructions

Folder undo points: create (dedup; skips .git/node_modules + exclude), list, diff, restore (auto-snapshots first; dry_run; path = restore elsewhere), delete.

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": {
      "op": "<op>"
    },
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
opYes
pathNo
labelNo
max_mbNo
dry_runNo
excludeNo
max_filesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose meaningful behavior: create deduplicates and skips .git/node_modules plus exclude patterns, and restore takes an automatic snapshot before overwriting. It omits safety-critical details such as whether delete is irreversible, what id is required for, and what the size/file limits (max_mb, max_files) do when exceeded.

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

Conciseness3/5

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

The single front-loaded line is dense and wastes no words, but the telegraphic style ('dedup', 'path = restore elsewhere') and stacked parentheses make it harder to parse than a couple of short sentences would be. Compressed to the point where clarity is traded away.

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?

For an 8-parameter tool with no annotations, no output schema, and zero schema descriptions, the definition should explain which parameters each operation needs and what is returned. Key gaps remain: id/label semantics, size and file-count limits, and any indication of destructive effects or response shape.

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 0%, and the description clarifies op values, exclude, dry_run, and the dual meaning of path (restore elsewhere), which is genuinely useful. It says nothing about id, label, max_mb, or max_files, and does not map parameters to the operations that require them, leaving half the surface undocumented.

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?

Names the resource precisely ('Folder undo points') and enumerates the five operations (create, list, diff, restore, delete), so an agent can tell it is a folder-snapshot manager rather than a generic file tool. It does not explicitly differentiate itself from siblings like 'diff' or 'archive', which overlap conceptually with its diff/create ops.

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?

The framing 'undo points' implies the use case (checkpoint a folder before risky changes, then restore), and a few inline notes hint at when options apply ('restore ... auto-snapshots first', 'dry_run', 'path = restore elsewhere'). There is no explicit when-to-use/when-not guidance or statement of prerequisites, leaving the agent to infer intent.

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