Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

checkpoint_save

Save a restart record with completed work, blockers, and next steps so Claude Free can resume after reaching its conversation limit.

Instructions

Save a restart/resume checkpoint for when Claude Free reaches its conversation limit.

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": {
      "title": "<title>",
      "summary": "<summary>",
      "nextSteps": "<nextSteps>"
    },
    "name": "checkpoint_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort checkpoint title
summaryYesCompleted work, current blockers and relevant context
nextStepsYesActions to do on resume

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, and the description is consistent with that. It adds useful framing by tying the write to the conversation-limit event, but says nothing about whether a save overwrites a prior checkpoint, where it persists, or how it is later retrieved. With annotations carrying the safety profile, this is adequate but not rich.

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?

A single front-loaded sentence that states the action first and the trigger second, with no filler or redundant restatement of the title. Every word earns its place.

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?

For a simple three-parameter write with full schema coverage and annotations, the description is sufficient to know what it does and when to call it. It is missing the lifecycle link — that the saved checkpoint is consumed by checkpoint_read/checkpoint_list — which an agent would need to complete the workflow without guessing.

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%, with every one of the three required parameters (title, summary, nextSteps) documented in-schema including the 20-item cap on nextSteps. The description adds no additional meaning about what belongs in summary or nextSteps or how much context is useful, so the baseline of 3 applies.

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

Purpose4/5

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

The description uses a specific verb and resource ('Save a restart/resume checkpoint'), so an agent can immediately tell this is a write-side persistence operation. It does not, however, distinguish itself from nearby siblings like checkpoint_list or checkpoint_read, which is the one thing keeping it from a 5.

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?

It supplies a concrete trigger condition — 'when Claude Free reaches its conversation limit' — which is exactly the situational context an agent needs before invoking it. It stops short of naming alternatives or stating when not to save (e.g. mid-task, redundant checkpoints), so it lands at 4 rather than 5.

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