Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

checkpoint_read

Read-only

Retrieve a saved checkpoint by ID or load the most recent one to resume work from a prior state.

Instructions

Read a saved checkpoint by ID, or the most recent one.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional checkpoint id; newest by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the defaulting rule, which duplicates the schema, and says nothing about behavior on an unknown/expired ID, whether reads are scoped to the current project, or what a checkpoint contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero waste and the default behavior front-loaded, which is good. It is arguably under-specified rather than verbose, and it carries no structure beyond a single clause.

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?

For a one-optional-parameter read-only tool with full schema coverage and no output schema, the definition plus annotations cover what an agent needs to invoke it correctly. Missing error-path and return-content notes are minor for a tool this simple.

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% and the single parameter is already documented as "Optional checkpoint id; newest by default," which the description merely restates in prose. No additional syntax, format, or validity information (e.g., where IDs come from) is contributed, so the baseline 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?

Specific verb ("Read") plus resource ("a saved checkpoint") with the default selection rule ("or the most recent one") stated in the same sentence. It is implicitly distinguishable from checkpoint_save/checkpoint_list, but it never names a sibling or explicitly contrasts with them, so it stops short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "Read a saved checkpoint" implies the use case, and the tool's only argument carries a default, so an agent can call it without further clarification. However, there is no explicit when-to-use or when-not guidance (for example, when to enumerate checkpoints first versus reading blind), and no mention of an alternative tool.

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