Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rebase_preset_branch

Destructive

Replays a decoration preset branch's versions onto another branch, then opens the result in Kiln's interactive 3D stage for orbit and zoom review.

Instructions

Rebase a decoration preset branch. 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": {
      "source_branch_id": "<source_branch_id>",
      "onto_branch_id": "<onto_branch_id>"
    },
    "name": "rebase_preset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorNoWho is performing the rebase, recorded on the event. Omit it to use the caller's own identity: on Kiln's servers the signed-in account (a different name is refused), locally the declared operator or the computer's user name.
onto_branch_idYesId of the decoration preset branch the replayed versions are appended to; its head ends at the source branch's head. Must be a different branch in the same graph.
source_branch_idYesId of the decoration preset branch whose versions above the common ancestor are replayed, oldest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / onto_branch_id / description
      Added value: +"Id of the decoration preset branch the replayed versions are appended to; its head ends at the source branch's head.  Must be a different branch in the same graph."
    • addedInput schema / properties / operator / description
      Added value: +"Who is performing the rebase, recorded on the event. Omit it to use the caller's own identity: on Kiln's servers the signed-in account (a different name is refused), locally the declared operator or the computer's user name."
    • addedInput schema / properties / source_branch_id / description
      Added value: +"Id of the decoration preset branch whose versions above the common ancestor are replayed, oldest first."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful context beyond annotations—Kiln Pro requirement, automatic stage opening, and mesh decimation for the stage—but it does not explain the core rebase consequences, such as history rewriting or conflict behavior.

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

Conciseness3/5

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

The purpose is front-loaded, but the inline 3D stage explanation is repeated across two paragraphs and is disproportionately long for a rebase tool. The structure is clear, yet the stage section could be tightened without losing essential information.

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 description covers the Pro requirement and the notable stage side effect, and the schema fully documents parameters. However, for a destructive branch operation it omits conflict handling, failure behavior, and how the source branch is affected, leaving meaningful gaps.

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 the input schema already documents source_branch_id, onto_branch_id, and operator in detail. The description adds no parameter-specific meaning beyond what the schema provides, which is the baseline expectation when schema coverage is complete.

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?

The description states a specific verb and resource: "Rebase a decoration preset branch." This clearly distinguishes it from rebase_design_branch and rebase_feature_branch by resource, though it does not explicitly name those siblings or contrast with merge_decoration_preset_branches.

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 description gives no when-to-use guidance versus alternatives such as merge_decoration_preset_branches or the design/feature rebase tools. "Needs Kiln Pro" is a prerequisite, not usage guidance, and there are no exclusions or conditions for choosing 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