Specky

Create Checkpoint

sdd_checkpoint

Creates a named snapshot of spec artifacts and pipeline state to enable rollback after major changes.

Instructions

Creates a named snapshot of all spec artifacts (CONSTITUTION.md, SPECIFICATION.md, DESIGN.md, TASKS.md, etc.) and the current pipeline state. Use before making major changes so you can rollback if needed.

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

Input Schema

Name	Required	Description	Default
`label`	No	Human-readable label for this checkpoint (e.g. 'before-redesign', 'v1-approved')
`spec_dir`	No	Spec directory path	.specs
`feature_number`	No	Feature number (e.g. '001')	001

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0-rc.14May 3, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations are all false, and description states it creates a snapshot (mutation). It does not disclose whether overwriting occurs if a checkpoint with the same label exists, nor does it detail side effects like pipeline state changes. Adequate but not thorough.

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?

Two sentences, front-loaded with purpose, then usage. Every word earns its place — no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not explain return values. It adequately covers what is captured and when to use it, but lacks details on rollback mechanism or pipeline state components. Sufficient for a simple snapshot tool.

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 parameters are well-documented in the schema. The description only adds minimal context (e.g., label examples) beyond the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states it 'Creates a named snapshot of all spec artifacts... and the current pipeline state', using a specific verb and resource. It distinguishes from sibling tools like sdd_restore (rollback) and sdd_list_checkpoints (list).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use before making major changes so you can rollback if needed', providing clear context for when to use. However, it does not mention when not to use or list alternatives.

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

Deploy Server