Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

export_model_3mf

Convert STL, OBJ, or GLB mesh files to 3MF format for modern slicers like PrusaSlicer, OrcaSlicer, and Bambu Studio; a compact ZIP-based XML format that supports metadata.

Instructions

Export a mesh to 3MF format (preferred by modern slicers).

        Converts STL/OBJ/GLB to 3MF, a ZIP-based XML format used by
        PrusaSlicer, OrcaSlicer, and Bambu Studio.  3MF is more compact
        and supports metadata better than STL.

        :param file_path: Path to the input mesh file.
        :param output_path: Output 3MF path.  Auto-generated if empty.
        :returns: Dict with the output file path.

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": {
      "file_path": "<file_path>"
    },
    "name": "export_model_3mf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the input mesh file.
output_pathNoOutput 3MF path. Auto-generated if empty. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the input mesh file."
    • changedInput schema / properties / output_path / description
      Previous value: -"Default: \"\"."New value: +"Output 3MF path.  Auto-generated if empty. Default: \"\"."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / output_path / default
      Removed value: -""
    • addedInput schema / properties / output_path / description
      Added value: +"Default: \"\"."
  3. First observedv0.1.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 mostly covered. The description adds useful context about supported input formats and 3MF's ZIP/XML nature, but it does not disclose behavior when the output path already exists, such as whether the tool overwrites the file or errors.

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 description is reasonably short and front-loads the core purpose, but it spends two sentences on ancillary format background and repeats the Sphinx-style parameter and return documentation already present in the schema. The duplicated :param: and :returns: block is unnecessary for an agent that already receives structured fields.

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 two-parameter export tool with annotations covering mutability and no output schema, the description is largely complete: it states the conversion capability, input formats, output-path fallback behavior, and return type. It could be stronger by clarifying overwrite behavior and how it relates to sibling 3MF-writing tools.

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 both parameters are already documented in the input schema. The description repeats the same parameter meanings, including output auto-generation, without adding format requirements, path constraints, or overwrite semantics beyond the schema.

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 states a specific verb and resource: exporting a mesh to 3MF, and explains that it converts STL/OBJ/GLB inputs. It does not clearly distinguish this from related 3MF-writing siblings such as wrap_gcode_as_3mf, compose_multicolor_3mf, 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?

It gives an implied reason to use this tool by noting 3MF is preferred by modern slicers and is more compact than STL. However, it offers no explicit when-to-use versus when-not-to-use guidance and does not name alternative export tools such as export_step or wrap_gcode_as_3mf.

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