Clarik Mcp Server

clarik_checkpoint_save

Save a structured checkpoint of your current session state, including goal, progress, decisions, and next steps, to resume work later without losing context.

Instructions

Generate a structured checkpoint of the current session state for resuming later.

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": {
      "goal": "<goal>",
      "progress": "<progress>",
      "decisions": "<decisions>",
      "nextStep": "<nextStep>"
    },
    "name": "clarik_checkpoint_save"
  }
}

Input Schema

Name	Required	Description
`goal`	Yes	Current working goal
`progress`	Yes	List of completed items
`decisions`	Yes	Key decisions made
`nextStep`	Yes	What to do next when resuming
`openFiles`	No	Currently open files
`openQuestions`	No	Unresolved questions
`projectPath`	No	Project root path for isolation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'structured checkpoint' without explaining side effects, whether it overwrites previous checkpoints, or any authorization needs. This leaves significant ambiguity about the tool's behavior.

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?

The description is a single sentence of 11 words, which is concise. However, it could be improved by including more guidance without being verbose. It earns a 4 because it is not wasteful but is missing content that would make it more useful.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what the checkpoint returns or how it affects the session. The lack of completeness means an agent may not understand when or why to invoke this 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 each parameter is already documented with descriptions. The tool description adds the context that this is a 'structured checkpoint' but does not provide additional meaning beyond the schema. Baseline of 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 the tool generates a structured checkpoint of the current session state for resuming later. The verb 'Generate' and resource 'checkpoint' are specific, and it distinguishes from the sibling 'clarik_checkpoint_resume' which handles resuming.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios (e.g., before closing a session), or when not to use it. Siblings like 'clarik_checkpoint_resume' imply a complementary action but no explicit when-to-use advice.

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