Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rename_decoration_preset_branch

Destructive

Rename a decoration-preset branch in Kiln Pro by providing its branch ID and a unique new name; use it to update branch labels without renaming retired branches.

Instructions

Rename a decoration-preset branch.

Needs Kiln Pro.

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": {
      "branch_id": "<branch_id>",
      "new_name": "<new_name>"
    },
    "name": "rename_decoration_preset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesThe branch's new name. Must not be empty and must not match another non-retired branch of the same preset (``BRANCH_EXISTS``).
branch_idYesId of the preset branch to rename. A retired branch cannot be renamed (``BRANCH_RETIRED``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds one piece of non-schema context — the Kiln Pro tier requirement — but says nothing about the effect of a rename on existing references, releases, or whether the old name remains resolvable.

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?

Two short lines with the action front-loaded and the prerequisite separated out. Nothing is wasted, though the prerequisite could carry a hint about where the tier is checked.

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?

For a two-parameter rename with full schema coverage, error codes documented, and no output schema, the definition covers what an agent needs to call it. The tier prerequisite is stated; only post-rename behavior on links/releases is left implicit.

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%, with both branch_id and new_name fully documented including error conditions (BRANCH_EXISTS, BRANCH_RETIRED). The description adds no meaning beyond the schema, so the 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?

States a specific verb and resource ('Rename a decoration-preset branch'), which clearly separates it from rename_decoration_preset (the preset itself) and retire_decoration_preset_branch. It stops short of naming those siblings explicitly, so an agent must infer the distinction from the name alone.

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 only guidance is the prerequisite 'Needs Kiln Pro', which is useful gating information but not when-to-use guidance. There is no statement about when to rename versus recreate a branch, or how this differs from retire/create siblings.

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