Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_decoration_preset_branches

Read-only

Lists the branches of a specified decoration preset, with an option to include retired branches. Use it to inspect available preset variants in Kiln Pro.

Instructions

List the branches of a decoration preset.

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": {
      "preset_id": "<preset_id>"
    },
    "name": "list_decoration_preset_branches"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYesId of the preset whose branches are listed.
include_retiredNoWhen true, retired branches are listed too. Off by default, so only live branches appear. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / include_retired / description
      Previous value: -"Default: false."New value: +"When true, retired branches are listed too. Off by default, so only live branches appear. Default: false."
    • addedInput schema / properties / preset_id / description
      Added value: +"Id of the preset whose branches are listed."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds one piece of non-obvious context, the Kiln Pro plan requirement, but does not say how a non-Pro caller fails (error vs. empty result) or whether pagination applies.

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 sentences with the core purpose front-loaded and zero filler. The trailing "Needs Kiln Pro." fragment is terse to the point of being unexplained, but it still earns its place as a gating requirement.

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 read-only two-parameter list tool with full schema coverage and safety annotations, the description covers the essentials: what is listed and the plan requirement. The only gap is routing relative to the many sibling branch/version/release listing tools.

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 both preset_id and include_retired are already fully explained, including the default-false behavior. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 gives a specific verb and resource ("List the branches of a decoration preset"), leaving no ambiguity about what is returned. It stops short of distinguishing this from adjacent list tools such as list_decoration_preset_releases, list_decoration_preset_versions, or list_design_branches, which an agent could easily confuse it with.

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?

"Needs Kiln Pro" is a prerequisite, not usage guidance. There is no statement of when to reach for this tool versus the sibling list_*_branches or preset-metadata tools, and no note on what to do when the preset has no branches.

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