Skip to main content
Glama

generate_ornament

Create a printable hanging ornament with optional text, photo or logo decoration, then preview it in an interactive 3D stage you can orbit and zoom.

Instructions

Generate a hanging ornament with optional decoration. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link). MAKE DOORS: design_session, Kiln's front door for making an object, is not installed here (signed in to Kiln it runs on Kiln's servers). On this install compile_scad IS the make → preview → iterate loop: make it, show the preview, iterate.

INLINE 3D STAGE: on success this tool opens Kiln's interactive 3D stage — an inline viewer panel the user can orbit, zoom, and turn over — in hosts that render MCP Apps panels (Kiln's hosted connection attaches a browser stage link for hosts that don't). Oversized meshes are decimated automatically for the stage; the PNG preview is the floor, not the whole experience.

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": "generate_ornament"
  }
}

Input Schema

NameRequiredDescriptionDefault
backNoBack face content — ``"plain"`` or ``"text:..."``. A photo or logo is refused here; it goes on ``front``. Default: "plain".
frontNoFront face content — ``"text:..."`` for debossed text, the path of a photo or logo to carve (on a star, inside its waist), or empty for plain. A file that is not there is refused. Default: "".
shapeNo``"circle"`` (default) or ``"star"``. Default: "circle".
brief_idNoOptional saved-goal id from ``design_session``. When supplied, the produced mesh gets a ``design_brief:<id>`` intent sidecar so the audit's "matches what you asked for" gate, the brief failure_history wiring, and the ``compare_design_versions`` intent diff all light up against the saved goal. Omit to skip — REST callers without a goal still get an auto-inferred brief at dispatch time. Default: "".
materialNoMaterial (default PLA). Default: "PLA".
body_colorNoBody color (default white). Default: "white".
photo_maskNoPhoto crop shape for a photograph (a logo on a clean field is carved unmasked whatever is passed; a name outside this list is refused) — ``"circle"``, ``"rectangle"`` or ``"rounded_rectangle"``. Empty follows the ornament's shape: a disc for both ``"circle"`` and ``"star"``. Default: "".
diameter_mmNoOuter diameter in mm (default 70). Default: 70.0.
star_pointsNoStar points (default 5, only for star shape). Default: 5.
include_stepNoAlso emit a CAD-exact STEP file. The STEP is REAL analytic B-rep built from the same typed parameters as the mesh — a true cylinder (or a true extruded star profile) with a real drilled hanging hole, the kind a machine shop's CAD opens clean, never a tessellated conversion. On success the response gains a ``step`` block with ``step_path``. Photo-front ornaments refuse the STEP honestly (heightmap relief has no analytic form) — the mesh outputs are always unaffected. Default: false.
thickness_mmNoThickness in mm (default 4, min 3). Default: 4.0.
color_overridesNoJSON dict mapping role → color name/hex. Overrides body_color for "body" role unless body_color is also set. Default: "".
hole_diameter_mmNoHanging hole diameter (default 3mm). Default: 3.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.5.1
    • changedInput schema / properties / back / description
      Previous value: -"Default: \"plain\"."New value: +"Back face content — ``\"plain\"`` or ``\"text:...\"``.  A photo or logo is refused here; it goes on ``front``. Default: \"plain\"."
    • changedInput schema / properties / body_color / description
      Previous value: -"Default: \"white\"."New value: +"Body color (default white). Default: \"white\"."
    • changedInput schema / properties / brief_id / description
      Previous value: -"Default: \"\"."New value: +"Optional saved-goal id from ``design_session``. When supplied, the produced mesh gets a ``design_brief:<id>`` intent sidecar so the audit's \"matches what you asked for\" gate, the brief failure_history wiring, and the ``compare_design_versions`` intent diff all light up against the saved goal.  Omit to skip — REST callers without a goal still get an auto-inferred brief at dispatch time. Default: \"\"."
    • changedInput schema / properties / color_overrides / description
      Previous value: -"Default: \"\"."New value: +"JSON dict mapping role → color name/hex. Overrides body_color for \"body\" role unless body_color is also set. Default: \"\"."
    • changedInput schema / properties / diameter_mm / description
      Previous value: -"Default: 70.0."New value: +"Outer diameter in mm (default 70). Default: 70.0."
    • changedInput schema / properties / front / description
      Previous value: -"Default: \"\"."New value: +"Front face content — ``\"text:...\"`` for debossed text, the path of a photo or logo to carve (on a star, inside its waist), or empty for plain.  A file that is not there is refused. Default: \"\"."
    • changedInput schema / properties / hole_diameter_mm / description
      Previous value: -"Default: 3.0."New value: +"Hanging hole diameter (default 3mm). Default: 3.0."
    • changedInput schema / properties / include_step / description
      Previous value: -"Default: false."New value: +"Also emit a CAD-exact STEP file.  The STEP is REAL analytic B-rep built from the same typed parameters as the mesh — a true cylinder (or a true extruded star profile) with a real drilled hanging hole, the kind a machine shop's CAD opens clean, never a tessellated conversion.  On success the response gains a ``step`` block with ``step_path``.  Photo-front ornaments refuse the STEP honestly (heightmap relief has no analytic form) — the mesh outputs are always unaffected. Default: false."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Material (default PLA). Default: \"PLA\"."
    • changedInput schema / properties / photo_mask / description
      Previous value: -"Default: \"\"."New value: +"Photo crop shape for a photograph (a logo on a clean field is carved unmasked whatever is passed; a name outside this list is refused) — ``\"circle\"``, ``\"rectangle\"`` or ``\"rounded_rectangle\"``. Empty follows the ornament's shape: a disc for both ``\"circle\"`` and ``\"star\"``. Default: \"\"."
    • changedInput schema / properties / shape / description
      Previous value: -"Default: \"circle\"."New value: +"``\"circle\"`` (default) or ``\"star\"``. Default: \"circle\"."
    • changedInput schema / properties / star_points / description
      Previous value: -"Default: 5."New value: +"Star points (default 5, only for star shape). Default: 5."
    • changedInput schema / properties / thickness_mm / description
      Previous value: -"Default: 4.0."New value: +"Thickness in mm (default 4, min 3). Default: 4.0."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (non-readonly, non-destructive, closed-world), the description discloses that a successful call opens an interactive 3D stage, that hosted sessions attach a browser stage link, and that oversized meshes are automatically decimated. The 'PNG preview is the floor, not the whole experience' line usefully frames what the user actually sees.

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 states the purpose cleanly, but the 'INLINE 3D STAGE' section restates the orbit/zoom panel and stage-link behavior already given in paragraph one, and the MAKE DOORS aside is tangential to this tool. Content is useful but padded by duplication.

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?

There is no output schema, yet the description never describes the returned payload (mesh path, preview image, the optional step block) beyond the stage experience. Parameter coverage is complete via the schema and behavior around the 3D stage is covered, but the response contract is left implicit for a 13-parameter generator.

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 front/back content, photo_mask, star_points, include_step, and the rest are already documented in the schema. The description adds only 'with optional decoration,' which does not extend meaning beyond the schema; the 100%-coverage 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 first sentence gives a specific verb and resource: 'Generate a hanging ornament with optional decoration.' That is enough to distinguish it from generic modeling tools, though nothing in the text separates it from the many sibling object generators such as generate_coaster, generate_keychain, or generate_pet_tag.

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?

The 'MAKE DOORS' paragraph discusses design_session and compile_scad, but never states when to call generate_ornament rather than another object generator, nor any when-not conditions. The routing note is about the surrounding ecosystem rather than about selecting or scoping this tool, so an agent gets no real usage guidance.

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