Skip to main content
Glama

deboss_during_print

Carve a debossed image into the top of an in-progress 3D print and generate carved G-code plus a resume package to continue the job.

Instructions

Carve a debossed image into the top of an in-flight print (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": {
      "image_path": "<image_path>",
      "gcode_path": "<gcode_path>",
      "current_layer": "<current_layer>"
    },
    "name": "deboss_during_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
bevelNoAdd a 1-layer bevel ring around the deboss for cleaner visual edges. Default ``True``. Default: true.
bed_tempNoBed setpoint for the 3MF metadata, read the same way as ``hotend_temp``.
depth_mmNoDeboss depth in mm. Must be in (0, 5]. Default: 1.2.
thresholdNoHeightmap value above which a pixel is treated as carved-away (0.0–1.0, default 0.35). Default: 0.35.
gcode_pathYesOriginal sliced .gcode of the in-flight job.
image_pathYesPNG/JPG to deboss into the top.
output_dirNoOutput directory for the carved + resume files. ``None`` uses the system temp dir.
top_layersNoReserved override for the top-layer count. ``None`` (default) uses the value detected from ``analyze_top_region`` (TYPE:Top tags or solid-infill inference).
hotend_tempNoHotend setpoint for the resume 3MF metadata. Leave unset to use the temperature the print's own file heats to; a value that differs from it is kept and said in ``warnings``.
image_scaleNoHeightmap-to-bed scale factor — 0.7 means the image fills 70% of the carved region's bounding box. Default: 0.7.
resume_z_mmNoExplicit resume Z height in mm. ``None`` means the resume scanner derives it from the carved G-code at ``current_layer + 1``.
aspect_policyNoHow to fit a non-matching aspect ratio onto the carve region. ``"auto_crop"`` crops the image to match (default), ``"auto_scale"`` letterboxes it, ``"strict"`` rejects mismatches. Default: "auto_crop".
current_layerYes1-indexed layer the printer is paused at. The deboss starts at ``current_layer + 1`` so the carve never touches the layer currently being laid down.
filament_typeNoThe print's material, for 3MF metadata. Leave it out and Kiln reads the print's own material; when nothing says which, the call is refused (``PRINT_MATERIAL_UNKNOWN``).
package_as_3mfNoWhen ``True`` (default), the tool also wraps the resume gcode as a Bambu resume-mode 3MF and returns its path as ``resume_3mf_path``. Disable for non-Bambu targets or when you want to inspect the carved gcode before packaging. On failure the error is surfaced via ``warnings`` — the .gcode path is still returned so the caller can recover. Default: true.
printer_z_knownNoREQUIRED ``True``. Same safety gate as ``generate_recovery_gcode`` — if the printer's Z isn't trustworthy, refuses with ``PRINTER_Z_UNKNOWN``. Default: false.
source_3mf_pathNoPassed through to the 3MF wrapper. Supplying the original job's .3mf preserves its thumbnail and 3D model preview on the printer's display. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv1.5.1
    • changedInput schema / properties / aspect_policy / description
      Previous value: -"Default: \"auto_crop\"."New value: +"How to fit a non-matching aspect ratio onto the carve region.  ``\"auto_crop\"`` crops the image to match (default), ``\"auto_scale\"`` letterboxes it, ``\"strict\"`` rejects mismatches. Default: \"auto_crop\"."
    • changedInput schema / properties / bed_temp / description
      Previous value: -"Default: 65."New value: +"Bed setpoint for the 3MF metadata, read the same way as ``hotend_temp``."
    • changedInput schema / properties / bevel / description
      Previous value: -"Default: true."New value: +"Add a 1-layer bevel ring around the deboss for cleaner visual edges.  Default ``True``. Default: true."
    • addedInput schema / properties / current_layer / description
      Added value: +"1-indexed layer the printer is paused at. The deboss starts at ``current_layer + 1`` so the carve never touches the layer currently being laid down."
    • changedInput schema / properties / depth_mm / description
      Previous value: -"Default: 1.2."New value: +"Deboss depth in mm.  Must be in (0, 5]. Default: 1.2."
    • changedInput schema / properties / filament_type / description
      Previous value: -"Default: \"PLA\"."New value: +"The print's material, for 3MF metadata. Leave it out and Kiln reads the print's own material; when nothing says which, the call is refused (``PRINT_MATERIAL_UNKNOWN``)."
    • addedInput schema / properties / gcode_path / description
      Added value: +"Original sliced .gcode of the in-flight job."
    • changedInput schema / properties / hotend_temp / description
      Previous value: -"Default: 220."New value: +"Hotend setpoint for the resume 3MF metadata.  Leave unset to use the temperature the print's own file heats to; a value that differs from it is kept and said in ``warnings``."
    • addedInput schema / properties / image_path / description
      Added value: +"PNG/JPG to deboss into the top."
    • changedInput schema / properties / image_scale / description
      Previous value: -"Default: 0.7."New value: +"Heightmap-to-bed scale factor — 0.7 means the image fills 70% of the carved region's bounding box. Default: 0.7."
    • addedInput schema / properties / output_dir / description
      Added value: +"Output directory for the carved + resume files.  ``None`` uses the system temp dir."
    • changedInput schema / properties / package_as_3mf / description
      Previous value: -"Default: true."New value: +"When ``True`` (default), the tool also wraps the resume gcode as a Bambu resume-mode 3MF and returns its path as ``resume_3mf_path``.  Disable for non-Bambu targets or when you want to inspect the carved gcode before packaging.  On failure the error is surfaced via ``warnings`` — the .gcode path is still returned so the caller can recover. Default: true."
    • changedInput schema / properties / printer_z_known / description
      Previous value: -"Default: false."New value: +"REQUIRED ``True``.  Same safety gate as ``generate_recovery_gcode`` — if the printer's Z isn't trustworthy, refuses with ``PRINTER_Z_UNKNOWN``. Default: false."
    • addedInput schema / properties / resume_z_mm / description
      Added value: +"Explicit resume Z height in mm.  ``None`` means the resume scanner derives it from the carved G-code at ``current_layer + 1``."
    • changedInput schema / properties / source_3mf_path / description
      Previous value: -"Default: \"\"."New value: +"Passed through to the 3MF wrapper. Supplying the original job's .3mf preserves its thumbnail and 3D model preview on the printer's display. Default: \"\"."
    • changedInput schema / properties / threshold / description
      Previous value: -"Default: 0.35."New value: +"Heightmap value above which a pixel is treated as carved-away (0.0–1.0, default 0.35). Default: 0.35."
    • addedInput schema / properties / top_layers / description
      Added value: +"Reserved override for the top-layer count. ``None`` (default) uses the value detected from ``analyze_top_region`` (TYPE:Top tags or solid-infill inference)."
  2. Addedv1.5.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the description's one sentence adds only the tier hint. For a high-risk operation that rewrites an in-flight job's G-code, the description says nothing about the resume file it produces, the safety refusals, or that failures surface as warnings while a .gcode path is still returned - all of that lives only in the parameter schema. No annotation contradiction is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than crisp summarization.

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 a 17-parameter, irreversible-feeling mid-print operation with no output schema, one sentence is far too thin: the agent gets no picture of the two-file return (carved G-code plus resume), the packaging/3MF behavior, or the safety gates. The rich schema compensates partly, but the description should orient the caller before they open it.

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%, with defaults, ranges, and error codes documented per parameter, so the baseline is 3. The description itself contributes no parameter meaning beyond 'image' and 'top', leaving the schema to do all the work.

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 names a specific verb and resource ('Carve a debossed image into the top of an in-flight print') and pins the operating mode (mid-print, not on a finished model), which an agent can distinguish from generic texture tools. However, it never names a sibling such as decorate_during_print or add_feature_during_print, so the agent must infer the boundary from the tool name alone.

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 / when-not-to-use guidance, no mention of prerequisites (paused print, trustworthy Z, known material), and no routing to alternatives for decorating versus adding features mid-print. The only usage signal is the '(Pro)' tier tag, which tells the agent about entitlement, not selection.

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