Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

batch_decorate

Apply the same text, image, or QR code decoration to multiple 3D models at once, with deboss or emboss options and automatic face selection.

Instructions

Apply the same decoration to multiple models (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": {
      "model_paths": "<model_paths>",
      "content": "<content>"
    },
    "name": "batch_decorate"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceNoWhich face to decorate on each model. ``"auto"`` (default) picks the largest flat face per model; also ``"top"``, ``"bottom"``, ``"front"``, ``"back"``, ``"left"``, ``"right"``, or, on a sketch-built part whose recipe sits beside the mesh, the sketch's own wall name (``"side:l2"``), which follows the wall through a resize and rebuild. Default: "auto".
modeNo``"deboss"`` (cut into the surface, default) or ``"emboss"`` (raised above it). Default: "deboss".
scaleNoShare of the face the decoration covers, 0.0-1.0 (default 0.7). Default: 0.7.
contentYesWhat to put on each surface: a PNG/JPG/SVG image path, ``"text:..."`` for text, or ``"qr:..."`` for a QR code.
depth_mmNoEmboss/deboss depth in mm. 0 (default) picks a depth for *material*. Default: 0.0.
materialNoMaterial the depth is tuned for (default ``"PLA"``). Default: "PLA".
output_dirNoFolder for the decorated files. Left out, a fresh temporary folder is used.
model_pathsYesThe models to decorate (STL or OBJ), one path each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • addedInput schema / properties / content / description
      Added value: +"What to put on each surface: a PNG/JPG/SVG image path, ``\"text:...\"`` for text, or ``\"qr:...\"`` for a QR code."
    • changedInput schema / properties / depth_mm / description
      Previous value: -"Default: 0.0."New value: +"Emboss/deboss depth in mm.  0 (default) picks a depth for *material*. Default: 0.0."
    • changedInput schema / properties / face / description
      Previous value: -"Default: \"auto\"."New value: +"Which face to decorate on each model.  ``\"auto\"`` (default) picks the largest flat face per model; also ``\"top\"``, ``\"bottom\"``, ``\"front\"``, ``\"back\"``, ``\"left\"``, ``\"right\"``, or, on a sketch-built part whose recipe sits beside the mesh, the sketch's own wall name (``\"side:l2\"``), which follows the wall through a resize and rebuild. Default: \"auto\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Material the depth is tuned for (default ``\"PLA\"``). Default: \"PLA\"."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"deboss\"."New value: +"``\"deboss\"`` (cut into the surface, default) or ``\"emboss\"`` (raised above it). Default: \"deboss\"."
    • addedInput schema / properties / model_paths / description
      Added value: +"The models to decorate (STL or OBJ), one path each."
    • addedInput schema / properties / output_dir / description
      Added value: +"Folder for the decorated files.  Left out, a fresh temporary folder is used."
    • changedInput schema / properties / scale / description
      Previous value: -"Default: 0.7."New value: +"Share of the face the decoration covers, 0.0-1.0 (default 0.7). Default: 0.7."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful '(Pro)' licensing signal, but leaves open whether source models are modified versus written to new files, and says nothing about per-model failures in a batch or quota limits despite a decoration_quota_status sibling existing.

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?

A single front-loaded sentence with the verb, scope and tier qualifier first, and no filler. Nothing redundant is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter batch mutation with no output schema, one sentence is thin. It omits whether the inputs are mutated or new files are produced, how partial failures are reported, and what the tier gate actually blocks, all of which an agent needs before committing a batch job.

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 every one of the 8 parameters (face, mode, scale, content, depth_mm, material, output_dir, model_paths) is already documented in detail. The description adds no parameter meaning beyond the schema, which is the baseline expectation at this coverage level.

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 ('Apply'), resource ('the same decoration') and scope ('multiple models'), which distinguishes it from the single-model apply_decoration or decorate_surface siblings by implication. It stops short of naming those alternatives explicitly, so the differentiation is inferential rather than stated.

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 batch scope implicitly signals when to reach for this tool over a single-model decoration call, and '(Pro)' flags a tier gate. But there is no explicit 'use this instead of X when Y', no mention of prerequisites beyond the parenthetical, and no guidance on batch failure handling or size limits.

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