Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

merge_mesh_files

Combine multiple STL files into a single mesh file for multi-part designs. Use it to compose printable assemblies; for x/y/z offset positioning, use the offset-aware merge tool instead.

Instructions

Combine multiple STL files into a single mesh file (simple concatenation).

        For positioning parts with x/y/z offsets, use ``merge_stl`` instead.
        Useful for composing multi-part designs into one printable file.

        :param file_paths: List of STL file paths to merge.
        :param output_path: Destination path for the merged file.
        :returns: Dict with merge statistics.

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": {
      "file_paths": "<file_paths>",
      "output_path": "<output_path>"
    },
    "name": "merge_mesh_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathsYesList of STL file paths to merge.
output_pathYesDestination path for the merged file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / file_paths / description
      Added value: +"List of STL file paths to merge."
    • addedInput schema / properties / output_path / description
      Added value: +"Destination path for the merged file."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the merge is concatenation only, it returns a dict of merge statistics, success opens an interactive 3D stage, and oversized meshes are auto-decimated for it. The main gap is that it never says what happens if output_path already exists (overwrite vs. error) — notable for a tool with destructiveHint=false that writes a file.

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?

Purpose and the sibling alternative are front-loaded in two tight sentences, but the Sphinx :param/:returns lines merely duplicate the schema and the 3D-stage paragraph is verbose relative to the one fact it carries (a viewer panel opens on success).

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?

With only two required params and no output schema, the description covers purpose, alternative, return shape, and a notable side effect (stage/decimation). Remaining unknowns — output overwrite semantics and whether merged parts keep their original relative origins — are small but real for a file-producing tool.

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% and the description's param notes just restate the schema wording verbatim. It adds no extra meaning such as a minimum number of files, unit/orientation assumptions, or whether paths must be pre-existing STLs — baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Combine multiple STL files into a single mesh file") and immediately qualifies the operation as "simple concatenation," which tells an agent exactly what kind of merge this is. It also names the sibling it is not (merge_stl) so the tool is distinguishable without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: for positioning parts with x/y/z offsets, use merge_stl instead. It adds a positive use case ("composing multi-part designs into one printable file"), so both the when and the when-not are covered.

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