Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_decoration_presets

Read-only

List current decoration presets for a design or portfolio-wide, with options to include archived presets.

Instructions

List the latest version of every decoration preset.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_decoration_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idNoId of a design: list that design's presets plus the portfolio-wide ones. Omit it to list every preset.
portfolio_onlyNoWhen true, list only portfolio-wide presets (those tied to no design); takes precedence over ``design_id``. Off by default. Default: false.
include_archivedNoWhen true, also list presets hidden by ``archive_decoration_preset``. Off by default. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"Id of a design: list that design's presets plus the portfolio-wide ones.  Omit it to list every preset."
    • changedInput schema / properties / include_archived / description
      Previous value: -"Default: false."New value: +"When true, also list presets hidden by ``archive_decoration_preset``.  Off by default. Default: false."
    • changedInput schema / properties / portfolio_only / description
      Previous value: -"Default: false."New value: +"When true, list only portfolio-wide presets (those tied to no design); takes precedence over ``design_id``.  Off by default. Default: false."
  2. Addedv1.5.0

TDQS

B3.3/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 the safety profile is covered. The description adds a meaningful behavioral fact beyond the annotations - the operation requires a Kiln Pro entitlement - and implies only latest versions are surfaced, but it says nothing about result size, pagination, or ordering.

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 with zero filler, and the core operation is front-loaded before the entitlement requirement. Nothing is repeated from the title or annotations.

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 read-only list tool with three fully documented, all-optional parameters and no output schema, the description is minimally adequate. It omits what a returned preset record looks like and whether results are paginated, which an agent would need in order to use the output intelligently.

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 design_id, portfolio_only, and include_archived are already fully explained, which sets the baseline at 3. The description's phrase 'the latest version of every decoration preset' adds a scoping semantic not in the schema (older versions excluded), but it does not clarify any individual parameter's behavior.

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 ('List ... every decoration preset') plus a scope qualifier ('the latest version of every'), so an agent knows the operation is a read-only enumeration of the newest preset revisions. It does not differentiate from closely named siblings such as list_decoration_preset_versions, list_decoration_preset_branches, or get_decoration_preset, which an agent could easily confuse with this tool.

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' gives a useful entitlement precondition for calling the tool, but there is no when-to-use guidance, no statement of when to prefer the version/branch/release listing siblings, and no mention that a design-scoped listing is available via the design_id parameter described in the schema.

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