Skip to main content
Glama

save_checkpoint

Save a repository handoff checkpoint with your note and current brief so other agents can resume work; optionally write a HANDOFF.md file into the repo.

Instructions

Save a handoff checkpoint (your note + the current brief) for this repository.

The checkpoint is stored under ~/.agent-history-mcp/checkpoints and shown by handoff_brief to any agent. apply=true also writes .agent-context/HANDOFF.md inside the repository.

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": {
      "note": "<note>"
    },
    "name": "save_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
applyNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the storage location (~/.agent-history-mcp/checkpoints), the cross-agent visibility of the saved checkpoint, and that apply=true performs an additional repo write to .agent-context/HANDOFF.md. It omits overwrite/append semantics and whether repeated saves clobber prior checkpoints, which is the main remaining risk for a write tool.

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?

Three short lines with the action and scope front-loaded, then storage behavior, then the side effect of apply. No filler or repetition.

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?

An output schema exists, so return values need not be described, and the description covers what is stored, where, who sees it, and the optional repo write. The gaps are the undocumented project parameter and the absence of any statement about overwriting existing checkpoints.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains note ("your note") and apply (writes HANDOFF.md inside the repo), but the third parameter, project, is never mentioned, leaving an agent to guess how it affects checkpoint scoping.

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?

States a specific verb and resource ("Save a handoff checkpoint") plus the scope ("for this repository") and what the checkpoint contains ("your note + the current brief"). It also names the sibling that surfaces the result (handoff_brief), so an agent can place it in the workflow without opening another schema.

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?

Usage context is clear: this is how you hand off state, and the result is visible to other agents via handoff_brief. It does not state when to avoid using it or contrast with siblings other than implicitly, but the intended moment of use is easy to infer.

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