Skip to main content
Glama

Restore draft checkpoint

restore_checkpoint
DestructiveIdempotent

Replaces your draft's files with an earlier checkpoint's; the old state stays in history. Pass get_current_work's checkpoint.id as expectedCurrentCheckpointId.

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": {
      "board": "<board>",
      "operationId": "<operationId>",
      "checkpointId": "<checkpointId>",
      "expectedCurrentCheckpointId": "<expectedCurrentCheckpointId>"
    },
    "name": "restore_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesYour board: handle/slug or a boardrepo.com URL.
operationIdYesClient-generated UUID. Reuse for retries of the same logical step; use a new one for a new edit or save.
checkpointIdYesA retained checkpoint from get_current_work history.
expectedCurrentCheckpointIdYesThe draft's current checkpoint.id before restore.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds the crucial non-obvious fact that the replaced state 'stays in history', i.e. the destruction is recoverable. It also reveals the optimistic-concurrency token requirement, though it does not say what happens on a mismatch or what permissions are needed.

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?

Two short clauses: the effect-and-recovery statement first, then the required value source. Nothing is redundant and no sentence is filler.

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 four-parameter, fully documented mutation with an output schema present, the description covers effect, recoverability, and the concurrency token's origin. What remains unexplained - failure mode on a stale expectedCurrentCheckpointId and any preconditions on the draft - is minor but not trivial for a destructive operation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description still adds meaning by tying expectedCurrentCheckpointId to a concrete source (get_current_work's checkpoint.id), clarifying which of the two UUIDs is the concurrency guard versus the restore target. operationId retry semantics are left entirely to the schema.

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 states a specific verb and resource ('Replaces your draft's files with an earlier checkpoint's') and immediately names the source of the target checkpoint, get_current_work, which separates it from sibling read/compare tools such as get_board and compare_board_versions.

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 gives an explicit prerequisite workflow - obtain the checkpoint id from get_current_work and pass it as expectedCurrentCheckpointId - which tells an agent how the call is sequenced. It does not state exclusions or when to prefer compare_board_versions or get_draft_operation first, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources