Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

retire_decoration_preset_branch

Destructive

Mark a decoration-preset branch as retired to remove it from active use. Requires Kiln Pro; team-owned presets can be retired only by team admins.

Instructions

Mark a decoration-preset branch retired.

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>"
    },
    "name": "retire_decoration_preset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_idYesId of the preset branch to retire. On a preset owned by a team the caller must hold that team's admin role, or the retire is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / branch_id / description
      Added value: +"Id of the preset branch to retire.  On a preset owned by a team the caller must hold that team's admin role, or the retire is refused."
  2. Addedv1.5.0

TDQS

A3.6/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 mutation profile is known. The description adds the Kiln Pro entitlement requirement, which is real context beyond the annotations, but it never says what 'retired' means operationally: whether it is reversible, what happens to child releases, or whether a retired branch still appears in list_decoration_preset_branches.

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

Conciseness5/5

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

Two short sentences, action first, prerequisite second. Nothing is wasted and the reader gets the core semantics before any qualification.

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 one-parameter mutation with rich annotations and no output schema, the essentials are present. The gap is that the irreversible/archival semantics of retirement are not explained, which is the main thing an agent would want to confirm before invoking a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers the single parameter at 100%, including the team-admin authorization caveat on branch_id, so the description does not need to restate it. It adds only the implicit constraint that the id must refer to a decoration-preset branch, which is marginal but consistent value above the schema.

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: 'Mark a decoration-preset branch retired.' The resource scope ('decoration-preset branch') is enough to separate it from siblings such as retire_design_branch and retire_feature_branch, but those alternatives are never named, so the differentiation is implicit rather than explicit.

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?

'Needs Kiln Pro' gives a hard prerequisite, which is genuinely useful gating information. However, there is no guidance on when to retire a branch rather than archive it (archive_decoration_preset, unarchive_decoration_preset exist) or how it relates to retire_decoration_preset_release, leaving the choice to inference.

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