Skip to main content
Glama

conductor_rollback

Verifies stored SHA-256 hashes and rolls a workspace back to a clean checkpoint, optionally previewing changes with a dry run before modifying disk.

Instructions

Verify stored SHA-256 hashes and roll back workspace to a clean checkpoint.

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": "conductor_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoRepository root path (defaults to cwd).
dry_runNoPreview files without modifying disk.
checkpoint_idNoOptional checkpoint ID (defaults to latest).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a destructive operation, and it falls short. It implies a safety gate via hash verification but never states what is destroyed (uncommitted edits, untracked files), whether rollback is reversible, or what happens when a hash mismatch is detected.

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 compact sentence with the destructive action stated up front and zero filler. It is efficient, though the merged verification clause costs a little clarity in exchange for brevity.

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 a workspace-mutating tool with no annotations, no output schema, and no indication of failure modes, the description is too thin. An agent cannot determine what a verify failure returns, whether prior state is recoverable, or what the call reports back.

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 all three parameters are already documented in the schema, establishing a baseline of 3. The phrase 'clean checkpoint' loosely corroborates the checkpoint_id default behavior, but the description adds no new syntax, format, or interaction detail beyond what the schema states.

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 a verb and resource ('roll back workspace to a clean checkpoint') but bundles a second operation ('verify stored SHA-256 hashes') into the same sentence without saying whether verification is a gate, a side effect, or a separate outcome. It also does not distinguish this from conductor_verify_drift, so an agent cannot tell which tool performs verification.

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 when-to-use or when-not-to-use guidance, no stated prerequisite that verification must pass first, and no routing to the sibling conductor_verify_drift. The dry_run parameter implies a preview workflow, but the description never mentions it.

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