Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

regenerate_3mf_thumbnail

Replace a 3MF file's embedded thumbnails with renders of a decorated STL so Bambu printer screens display the applied decoration.

Instructions

Swap the embedded thumbnails in a 3MF for renders of a decorated STL so the Bambu screen shows the decoration (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": {
      "three_mf_path": "<three_mf_path>",
      "decorated_stl_path": "<decorated_stl_path>"
    },
    "name": "regenerate_3mf_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex colour for the STL render. Defaults to white. Default: "#FFFFFF".
output_pathNoWhere to write the re-thumbnailed 3MF. Empty = ``{three_mf_path}_with_thumbnails.3mf``. Default: "".
three_mf_pathYesSource 3MF (typically the engine's transformed_resume_path).
decorated_stl_pathYesSTL whose render becomes the 3MF's thumbnail PNGs. Typically the ``stl_path`` from a prior ``preview_decorated_mesh`` call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / color / description
      Previous value: -"Default: \"#FFFFFF\"."New value: +"Hex colour for the STL render.  Defaults to white. Default: \"#FFFFFF\"."
    • addedInput schema / properties / decorated_stl_path / description
      Added value: +"STL whose render becomes the 3MF's thumbnail PNGs.  Typically the ``stl_path`` from a prior ``preview_decorated_mesh`` call."
    • changedInput schema / properties / output_path / description
      Previous value: -"Default: \"\"."New value: +"Where to write the re-thumbnailed 3MF.  Empty = ``{three_mf_path}_with_thumbnails.3mf``. Default: \"\"."
    • addedInput schema / properties / three_mf_path / description
      Added value: +"Source 3MF (typically the engine's transformed_resume_path)."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already state readOnly=false, destructive=false, openWorld=false, so safety posture is covered. The description usefully adds the '(Pro)' entitlement flag and the user-visible outcome, but omits whether the source 3MF is modified versus a new file being written and whether anything other than thumbnails is touched.

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 sentence with the action front-loaded and the rationale appended; nothing is padding, and the '(Pro)' qualifier is placed at the end where it does not obstruct reading.

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 four-parameter tool with no output schema, the description supplies the intent and the visible result, while the schema handles paths, colors, and defaults. The main residual gap is the ordering relationship to the decoration/preview step, which an agent must infer from the schema alone.

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 all four parameters (including color default and output_path fallback) are already documented. The description adds no parameter-level meaning beyond the schema, which is the expected baseline here.

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 pair ('swap the embedded thumbnails in a 3MF for renders of a decorated STL') and states the end goal (Bambu screen showing the decoration). That is enough to distinguish it from mesh-editing or gcode-wrapping siblings, though it never explicitly contrasts with nearby tools like preview_decorated_mesh or embed_manual_in_3mf.

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?

Usage is only implied: you do this after a mesh is decorated so the printer's screen preview matches. There is no explicit when-to-use/when-not, no statement that preview_decorated_mesh should run first (that link lives only in the parameter schema), and no note about when regeneration is unnecessary.

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