Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

add_qr_to_product

Add a scannable QR code to a product STL for 3D printing, with placement, size, and nozzle-aware module sizing, then open an interactive 3D stage to inspect the result.

Instructions

Add a scannable QR code to any product STL (Business). Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link).

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

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": {
      "product_stl_path": "<product_stl_path>",
      "qr_content": "<qr_content>"
    },
    "name": "add_qr_to_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
size_mmNoQR size override in mm (0 = auto from product). Default: 0.
nozzle_mmNoNozzle diameter in mm; the QR's smallest module is sized from it so the code prints cleanly. Leave unset to use the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which was used.
placementNo``'bottom'``, ``'top'``, or ``'pocket'``. Default: "bottom".
qr_contentYesURL or text to encode in the QR code.
product_typeNoTemplate key for profile lookup (optional). Default: "".
pad_height_mmNoHeight of the QR pads in mm, default 0.5. Default: 0.5.
product_stl_pathYesPath to the base product STL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • addedInput schema / properties / nozzle_mm / description
      Added value: +"Nozzle diameter in mm; the QR's smallest module is sized from it so the code prints cleanly. Leave unset to use the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which was used."
    • changedInput schema / properties / pad_height_mm / description
      Previous value: -"Default: 0.5."New value: +"Height of the QR pads in mm, default 0.5. Default: 0.5."
    • changedInput schema / properties / placement / description
      Previous value: -"Default: \"bottom\"."New value: +"``'bottom'``, ``'top'``, or ``'pocket'``. Default: \"bottom\"."
    • addedInput schema / properties / product_stl_path / description
      Added value: +"Path to the base product STL."
    • changedInput schema / properties / product_type / description
      Previous value: -"Default: \"\"."New value: +"Template key for profile lookup (optional). Default: \"\"."
    • addedInput schema / properties / qr_content / description
      Added value: +"URL or text to encode in the QR code."
    • changedInput schema / properties / size_mm / description
      Previous value: -"Default: 0."New value: +"QR size override in mm (0 = auto from product). Default: 0."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the write/safety profile: readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds useful behavior about opening an inline 3D stage, hosted browser links, and automatic decimation for oversized meshes. However, it does not say whether the original STL is modified or a new artifact is created, nor where the result is written, leaving a core mutation detail undisclosed.

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 purpose is front-loaded, but the inline 3D stage behavior is described twice in quick succession. The 'PNG preview is the floor' phrasing is colorful but not essential, and the repetition weakens conciseness.

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 7-parameter mutation tool with no output schema, the description covers the visible stage behavior but omits key operational details such as the output artifact/path and whether the source STL is preserved. It is adequate but not complete.

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 parameter is already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline 3 is appropriate.

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: 'Add a scannable QR code to any product STL,' and adds the Business tier context. It is clear what the tool does, but it does not explicitly differentiate itself from similar siblings such as generate_qr_decoration.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternatives. The only contextual cue is 'Business' and applicability to product STLs, which implies usage but does not guide selection among related tools.

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