Clarik Mcp Server

clarik_checkpoint_resume

Resume previous work by loading the latest or a specific checkpoint for a given project path.

Instructions

Load the most recent checkpoint (or a specific one) to resume work.

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

Input Schema

Name	Required	Description	Default
`checkpointId`	No	Specific checkpoint ID to resume (default: latest)
`projectPath`	No	Project root path for isolation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries full burden but does not disclose behavioral traits such as whether current state is replaced, if other tools are affected, or if permissions are needed. The term 'resume' is vague.

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?

The description is a single sentence of 12 words, conveying the core functionality efficiently without unnecessary details.

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?

While the description is clear for a simple tool, it lacks details on return behavior, side effects, or integration with other checkpoint tools. Given the complexity of checkpoint management, more context would aid correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by stating the default for checkpointId (latest) and explaining projectPath for isolation, which are not explicit in the schema descriptions.

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 the tool loads a checkpoint to resume work, specifying both the most recent and a specific one. It distinguishes from sibling clarik_checkpoint_save by focusing on resuming rather than saving.

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?

No guidance is provided on when to use this tool versus alternatives like clarik_checkpoint_save or clarik_context_trim. There is no mention of prerequisites or scenarios to avoid.

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