Skip to main content
Glama

restore_checkpoint

Upload a locally saved checkpoint file into a run's checkpoints directory on the runtime to resume training or recover prior model state.

Instructions

Upload a locally-saved checkpoint file back into a run's checkpoints/ dir on the runtime.

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": {
      "run_name": "<run_name>",
      "local_filename": "<local_filename>"
    },
    "name": "restore_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_nameYes
local_filenameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says where the file lands, but says nothing about overwrite behavior (does it replace an existing checkpoint of the same name?), required permissions, size limits, or whether the target run must be active on the runtime.

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?

A single sentence with no wasted words, and the destination path is front-loaded. It is efficient, though slightly terse given the gaps it needs to close.

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?

The output schema exists, so return values need not be explained, and the two parameters are named. Still missing are the preconditions for a restore (run existence, overwrite semantics), which matter for a file-placement mutation.

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 should compensate, yet it adds no meaning beyond the parameter names. It does not clarify whether local_filename is a path or a bare name, or what form run_name takes (ID, slug, display name).

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?

States a specific verb (upload/restore) and resource (a locally-saved checkpoint file) plus the destination ('a run's checkpoints/ dir on the runtime'), which clearly makes it the inverse of save_checkpoint. It does not explicitly name that sibling, but the resource and direction are unambiguous.

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 'back into a run's checkpoints/' implies the use case: reinstating a checkpoint that was previously saved locally. However, there is no explicit when-to-use/when-not guidance, no mention of save_checkpoint as the counterpart, and no stated prerequisites such as whether the run must already exist.

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