Skip to main content
Glama

restore_checkpoint

Destructive

Restore a workflow to a saved checkpoint: its steps (and its name, description and settings as they were) come back as a new version, and the triggers of the steps it brings back register again. Steps it takes away are torn down with what they held.

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": {
      "workflow_id": "<workflow_id>",
      "checkpoint_id": "<checkpoint_id>"
    },
    "name": "restore_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflow_idYes
checkpoint_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description earns credit by explaining concretely what destruction means: removed steps are 'torn down with what they held,' and restored content arrives as a new version with triggers re-registering. It omits permission/auth requirements and any reversibility note, so it stops short of 5.

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

Conciseness4/5

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

One dense, front-loaded sentence that states the operation first and the side effects second; every clause carries information. The parenthetical about name, description and settings makes the sentence slightly convoluted but is not wasteful.

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?

With an output schema present and annotations carrying the safety profile, the description supplies the missing behavioral picture: new-version semantics, trigger re-registration, and teardown of removed steps. The remaining gap is that it gives no hint about where the two required IDs come from, which matters for a destructive tool.

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% and neither workflow_id nor checkpoint_id is mentioned in the description. The prose implies the concepts of 'workflow' and 'checkpoint' but adds no format, source, or constraint information, leaving the description to fail its compensation duty for two undocumented required parameters.

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?

Names a specific verb and resource ('Restore a workflow to a saved checkpoint') and immediately describes the resulting state, so the agent knows exactly what operation it is. It does not distinguish itself from checkpoint siblings like list_checkpoints or create_checkpoint, which keeps it 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?

Usage is only implied: the mention of 'a saved checkpoint' suggests the agent needs a checkpoint_id obtained elsewhere, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer intent from the name but gets no routing guidance.

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.