Skip to main content
Glama

driftguard_selective_rollback

Restore specific files from a workspace snapshot while preserving healthy files created since. Provide targeted file paths to roll back risky changes without affecting unrelated work.

Instructions

Rollback di precisione: ripristina esclusivamente un elenco mirato di file specifici dallo snapshot, preservando i file sani creati nel frattempo.

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": {
      "targetFiles": "<targetFiles>"
    },
    "name": "driftguard_selective_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshotIdNoID facoltativo dello snapshot sorgente (default: più recente).
targetFilesYesArray dei percorsi relativi dei file da ripristinare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the blast radius — only the listed files are touched and other files are preserved — which is genuinely useful. However, it never says whether existing versions of the target files are overwritten, whether the action is reversible or whether a checkpoint is taken first.

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 dense sentence with the operative concept front-loaded (

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 potentially destructive mutation tool with no annotations and no output schema, the description covers purpose and scope but leaves gaps around safety prerequisites (preview/dry-run), overwrite semantics and recoverability. An agent could invoke it correctly but not confidently.

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%, so both params (snapshotId with default-most-recent, targetFiles as relative paths) are already documented in the schema. The description only restates that the file list is 'targeted' and that a snapshot is the source, adding no new meaning.

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?

States a specific verb+resource: it restores only a targeted list of files from a snapshot and preserves healthy files created afterward. The word 'selective' and the scoping clause distinguish it from the full-rollback sibling driftguard_rollback, though that sibling is never named explicitly.

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 implied use case is clear (restore from a snapshot, but only specific files), but there is no explicit when-to-use/when-not guidance, no mention of driftguard_rollback as the full alternative, and no suggestion to run driftguard_preview_rollback first.

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