Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

compose_models

Merge multiple STL, OBJ, or GLB mesh files into a single combined model by concatenating triangle geometry. Use it to assemble multi-part designs or add components without boolean operations.

Instructions

Merge multiple mesh files into a single combined model.

        Concatenates all triangle geometry from the input files into one
        output STL.  No boolean operations — bodies are simply combined.
        Useful for multi-part assemblies or adding components to a design.

        **See also:** ``merge_mesh_files`` for the same operation with
        a different parameter style, or ``merge_stl`` for positional
        offset support.

        :param file_paths: List of .stl/.obj/.glb file paths to merge.
        :param output_path: Path for the combined output STL.
        :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": "compose_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathsYesList of .stl/.obj/.glb file paths to merge.
output_pathYesPath for the combined output STL.

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/.obj/.glb file paths to merge."
    • addedInput schema / properties / output_path / description
      Added value: +"Path for the combined output STL."
  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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, but the description adds meaningful behavior: geometry is concatenated without booleans, output is an STL, and a success opens an interactive 3D stage with automatic decimation for oversized meshes. It does not state whether an existing output_path is overwritten or whether input files remain untouched, which keeps it from a 5.

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?

The purpose is front-loaded and the See also routing follows immediately, so the structure is easy to scan. The RST :param: lines duplicate the schema and the stage paragraph is verbose, but the latter conveys non-obvious side-effect behavior rather than filler.

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 merge tool with no output schema, the description covers the operation, supported input formats, output format, alternatives, and the inline 3D stage side effect. The return value is only described as 'Dict with merge statistics,' which is somewhat vague, but the core invocation context is 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%, and the description largely repeats the schema's parameter text for file_paths and output_path. It adds supported formats (.stl/.obj/.glb) and output format (STL), but these are already present or closely implied by the schema.

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?

The description states a specific verb and resource: merge multiple mesh files into a single combined model. It also explicitly distinguishes the operation from boolean composition by saying bodies are simply concatenated, and names sibling alternatives merge_mesh_files and merge_stl.

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?

It gives concrete usage context ('multi-part assemblies or adding components') and routes the agent to alternatives by explaining that merge_mesh_files has a different parameter style while merge_stl supports positional offsets. The 'No boolean operations' note also implicitly distinguishes it from boolean_mesh_op-style 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