Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

iterate_decoration

Create a new version of a saved decoration while archiving the current one, so you can tune depth, mode, style, or content files and still roll back to the previous version.

Instructions

Create a new version of a saved decoration, archiving the current one (Kiln Pro).

        Use this when tuning a decoration -- a new depth, mode, style or
        content file -- and the previous version stays available for
        ``rollback_decoration``.

        :param name: Decoration name or slug.
        :param content_path: New content file (empty = keep current).
        :param depth_mm: New depth in mm (0 = keep current).
        :param mode: New mode, ``emboss`` or ``deboss`` (empty = keep current).
        :param image_style: New image style (empty = keep current).
        :param notes: Free-text notes for this iteration.
        :returns: Dict with the new version and what changed.

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

Input Schema

NameRequiredDescriptionDefault
modeNoNew mode, ``emboss`` or ``deboss`` (empty = keep current). Default: "".
nameYesDecoration name or slug.
notesNoFree-text notes for this iteration. Default: "".
depth_mmNoNew depth in mm (0 = keep current). Default: 0.0.
image_styleNoNew image style (empty = keep current). Default: "".
content_pathNoNew content file (empty = keep current). Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • changedInput schema / properties / content_path / description
      Previous value: -"Default: \"\"."New value: +"New content file (empty = keep current). Default: \"\"."
    • changedInput schema / properties / depth_mm / description
      Previous value: -"Default: 0.0."New value: +"New depth in mm (0 = keep current). Default: 0.0."
    • changedInput schema / properties / image_style / description
      Previous value: -"Default: \"\"."New value: +"New image style (empty = keep current). Default: \"\"."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"\"."New value: +"New mode, ``emboss`` or ``deboss`` (empty = keep current). Default: \"\"."
    • addedInput schema / properties / name / description
      Added value: +"Decoration name or slug."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Free-text notes for this iteration. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive mutation, and the description adds context they cannot carry: the current version is archived rather than destroyed and stays reachable via rollback_decoration, and the '(Kiln Pro)' marker signals a tier requirement. It also notes the return is a dict of the new version plus what changed; pagination/idempotency are not discussed but are not relevant here.

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 opening sentence is crisp and front-loads the key behavior, and usage guidance follows immediately. However, the ':param' block duplicates the input schema word for word and the ':returns:' line restates what could be inferred, consuming space without adding information.

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 6-parameter mutation with no output schema, the description covers the important angles: what gets archived, that rollback remains possible, the keep-current sentinel convention, and the shape of the response. Only the paid-tier gating is left as an unexplained parenthetical.

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% and the description's ':param' block repeats the schema text almost verbatim, including the 'empty/0 = keep current' sentinel convention. It adds essentially no meaning beyond the schema, so the baseline of 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?

The description states a specific verb and resource: 'Create a new version of a saved decoration, archiving the current one.' That distinguishes it from a plain save and from apply_decoration, and it names rollback_decoration as the counterpart. It stops short of explicitly contrasting with save_decoration, the closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this when tuning a decoration -- a new depth, mode, style or content file' gives a clear triggering condition tied to what changes. It does not say when not to use it or name save_decoration as the alternative for non-iterative edits, so it is clear context rather than a full routing rule.

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