Skip to main content
Glama

save_checkpoint

Save a progress checkpoint after each concrete sub-task. Future agent sessions resume exactly from this point, avoiding redoing completed work.

Instructions

Save a progress checkpoint so any future agent session can resume exactly here.

Call this after EVERY concrete sub-task (a file edited, a test passing, a command run) — not only when a numbered step finishes. Frequent, small checkpoints are the point: if the session dies mid-step, the next agent resumes from the last sub-task instead of redoing the whole step.

Args: plan: The full numbered plan being executed (all steps, verbatim). current_step: 1-based number of the step currently being worked on. total_steps: Total number of steps in the plan. step_status: "in_progress", "done", or "blocked" — status of current_step. what_was_done: Everything completed so far, across all steps, specific enough that another agent will not redo any of it. what_remains: What is still missing IN THE CURRENT STEP, specific enough to be the very next action (plus any known remaining steps). project_dir: Optional project directory override; defaults to the server's working directory (walking up to the nearest .git root).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
project_dirNo
step_statusYes
total_stepsYes
current_stepYes
what_remainsYes
what_was_doneYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the purpose and parameter roles, but does not specify whether it overwrites existing checkpoints or enforces any constraints like uniqueness per step.

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?

Well-structured: a concise purpose sentence, followed by usage guidance, then a clearly labeled Args section. Every sentence adds value.

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

Completeness5/5

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

Given the complexity (7 parameters, no annotations, no schema descriptions), the description provides complete guidance on purpose, usage, and parameter semantics. The presence of an output schema covers return values.

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

Parameters5/5

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

Schema has zero descriptions for parameters (0% coverage). The description compensates fully with a detailed Args section explaining the meaning and expected content of each parameter, including optional project_dir.

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's purpose: 'Save a progress checkpoint so any future agent session can resume exactly here.' It distinguishes itself from sibling tools (clear, get, list) by focusing on creation.

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?

Explicit guidance on when to call: 'Call this after EVERY concrete sub-task...Frequent, small checkpoints are the point.' It implies not to call only at step boundaries, but does not explicitly address when not to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DiegoWare/agent-checkpoint-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server