Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

restore_from_reflog_entry

Destructive

Restore a branch to a recorded head state using a reflog entry, undoing or redoing a prior operation in your 3D design history.

Instructions

Snap a branch back to a recorded head state.

Free door, tiered answer — Free: Branch · merge · cherry-pick · undo, on the designs you keep · Pro: Branch · merge · cherry-pick · undo, on every design · Business: ✓ · Enterprise: ✓.

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": {
      "reflog_id": "<reflog_id>"
    },
    "name": "restore_from_reflog_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo``"old_head"`` (the default) to undo the recorded operation, or ``"new_head"`` to redo it; anything else is refused. Default: "old_head".
operatorNoWho is making the change, recorded on the restore entry. On Kiln's servers it must match the signed-in account (a different name is refused); omitted, the signed-in account, or on a local install the local operator.
reflog_idYesThe entry to restore from, as ``show_reflog`` returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / operator / description
      Added value: +"Who is making the change, recorded on the restore entry. On Kiln's servers it must match the signed-in account (a different name is refused); omitted, the signed-in account, or on a local install the local operator."
    • addedInput schema / properties / reflog_id / description
      Added value: +"The entry to restore from, as ``show_reflog`` returns it."
    • changedInput schema / properties / target / description
      Previous value: -"Default: \"old_head\"."New value: +"``\"old_head\"`` (the default) to undo the recorded operation, or ``\"new_head\"`` to redo it; anything else is refused. Default: \"old_head\"."
  2. Addedv1.5.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the key safety signal is covered. The description adds nothing beyond that: it does not say whether the restore writes a new reflog entry, what happens to the working tree, or whether confirmation/dry-run is possible. The tier paragraph occupies space that should have carried this behavioral content.

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

Conciseness2/5

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

The first sentence is well front-loaded and economical. The second sentence, a Free/Pro/Business/Enterprise marketing listing that is identical noise across many tools, earns no place in a tool definition and dilutes attention.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive history-rewriting operation with no output schema and no annotations explaining reversibility, so the description carries real burden. It omits what the restore produces, whether it is reversible, and any authorization requirement, leaving the agent dependent on the schema alone.

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 parameter docs are already rich (target old_head/new_head with 'anything else is refused', operator must match the signed-in account). The description adds no meaning beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

"Snap a branch back to a recorded head state" gives a verb and a resource, so the general action is inferable, but the phrasing is idiomatic rather than precise ("snap" could mean move, reset, or re-attach). It never distinguishes this from close siblings such as undo_last_head_change, show_reflog, or get_reflog_entry, which an agent must choose between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this versus undo_last_head_change or show_reflog, and no prerequisites or preconditions are given. The only additional prose is a paid-tier feature list that has nothing to do with selecting this tool.

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

Deploy Server

Other Tools