Skip to main content
Glama

conductor_create_checkpoint

Creates an atomic SHA-256 verified workspace snapshot before risky edits, enabling rollback to a known-good state when changes break tests or syntax.

Instructions

Create an atomic SHA-256 verified workspace snapshot before risky edits.

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_create_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoRepository root path (defaults to cwd).
labelNoHuman-readable checkpoint label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does contribute real behavioral facts: the snapshot is atomic and integrity-verified via SHA-256. It is silent on cost/size, whether it writes files into the workspace, where the snapshot is stored, and whether checkpoints expire or can be overwritten by a same-label call.

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?

One sentence, zero filler, and the key qualifiers (atomic, SHA-256 verified, before risky edits) are front-loaded. Nothing could be removed without losing signal.

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 two-optional-parameter tool with no annotations and no output schema, the description is adequate on what it does but leaves the return value unexplained — the agent cannot tell whether it receives a checkpoint ID, a path, or a hash, which matters for later rollback. Slightly more would be warranted given zero structured support.

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% and both parameters already document their meaning (root defaults to cwd, label is human-readable), so the baseline applies. The description adds no guidance on how the label affects retrieval or rollback, which would have been the one place to add value beyond the schema.

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 ('Create') and a precisely characterized resource ('atomic SHA-256 verified workspace snapshot'), which tells an agent exactly what artifact is produced. It does not explicitly distinguish itself from siblings like conductor_lock_baseline, but the 'snapshot' framing is distinct enough to be actionable.

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 phrase 'before risky edits' gives a genuine timing cue for when to call it, which is more than most mutation tools offer. However, it never contrasts with the obvious alternatives in the sibling set (lock_baseline, rollback) or states prerequisites, so the agent must infer the choice.

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