Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rollback_feature

Destructive

Restore an earlier design version by appending its content as a new version, preserving full history. Use it to revert a 3D model to a known-good state before further edits.

Instructions

Append a new version whose content matches an earlier version. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link).

Needs Kiln Pro.

INLINE 3D STAGE: on success this tool opens Kiln's interactive 3D stage — an inline viewer panel the user can orbit, zoom, and turn over — in hosts that render MCP Apps panels (Kiln's hosted connection attaches a browser stage link for hosts that don't). Oversized meshes are decimated automatically for the stage; the PNG preview is the floor, not the whole experience.

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": {
      "feature_id": "<feature_id>",
      "feature_version_id": "<feature_version_id>"
    },
    "name": "rollback_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional operator note; defaults to ``"Rollback to v<N>"``. Default: "".
feature_idYesThe stable feature id.
feature_version_idYesVersion to roll back TO.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / feature_id / description
      Added value: +"The stable feature id."
    • addedInput schema / properties / feature_version_id / description
      Added value: +"Version to roll back TO."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Optional operator note; defaults to ``\"Rollback to v<N>\"``. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description adds genuinely useful nuance: the operation appends a new version rather than deleting history, so prior versions survive. It also discloses the Kiln Pro licensing gate and the rendering side effects (stage opens on success, oversized meshes are decimated, hosted sessions get a browser link). It does not state required permissions or whether branches are affected.

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 inline 3D stage point is made twice — parenthetically in the first sentence and again in a dedicated all-caps section that restates the orbit/zoom panel, the browser link fallback, and the decimation behavior. The mechanism and licensing facts are buried under viewer marketing prose that crowds out missing usage guidance.

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?

For a destructive mutation with no output schema, the description covers the mechanism, licensing, and rendering side effects, which is a reasonable baseline. It omits how to discover a valid feature_version_id, what failure modes exist (unknown version, tier not entitled), and whether the rollback affects the feature's current branch pointer.

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%, so feature_id, feature_version_id, and notes are already documented, including the default note text. The description adds no semantics beyond the schema — no guidance on where a version id comes from or what happens if the target version predates a branch point. 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?

"Append a new version whose content matches an earlier version" states a concrete mechanism and verb, and it usefully reframes rollback as a history-appending operation rather than an in-place overwrite. It never names the resource ("feature") in the description, and it does not distinguish itself from siblings such as rollback_design_version, rollback_decoration, restore_from_reflog_entry, or undo_last_head_change.

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?

The only conditional guidance is "Needs Kiln Pro," which is a real prerequisite worth stating. There is no guidance on when to roll back versus using undo_last_head_change or restore_from_reflog_entry, no note that a version id must first be obtained from list_feature_versions, and no when-not-to-use exclusions.

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