Skip to main content
Glama

merge_stl

Merge multiple STL files into a single mesh, with optional positional offsets for each part.

Instructions

Merge multiple STL files into a single mesh (supports positional offsets).

Use this when you need to position parts relative to each other.
For simple concatenation without positioning, ``merge_mesh_files`` also works.
Combines triangle data from multiple STL files into one output file.
Optionally translates each part to a specified position before merging.

:param file_paths: JSON array of STL file paths.
:param output_path: Where to write the merged STL.
:param positions: Optional JSON array of {"x", "y", "z"} offsets per file.
:returns: Dict with output_path, total_triangles, bounding_box.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
positionsNo
file_pathsYes
output_pathYes
Behavior4/5

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

The description explains that it combines triangle data and optionally translates each part. It also mentions the return dict. However, it does not discuss error handling, file existence requirements, or permissions. Since no annotations are provided, the description carries the full burden. It provides a good baseline but could be more detailed on edge cases.

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?

The description is concise (only a few sentences) and well-structured: a clear purpose statement, usage guidance, and then parameter documentation. Every sentence adds value without redundancy.

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?

Given no output schema, the description includes the return type (dict with output_path, total_triangles, bounding_box). It covers all inputs and the alternative tool. It is complete for a simple file-merging tool but could be improved by mentioning potential errors or limitations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage (all parameters are strings with no documentation). The description fully compensates by documenting each parameter: file_paths as JSON array of STL paths, output_path as write destination, and positions as optional JSON array of xyz offsets with default. This adds significant meaning beyond the bare 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 'Merge multiple STL files into a single mesh (supports positional offsets).' This clearly defines the verb (merge) and resource (STL files) with a key feature (positional offsets). It also distinguishes from the sibling tool merge_mesh_files by specifying that this tool is for positioning parts relative to each other.

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?

The description explicitly says 'Use this when you need to position parts relative to each other' and provides an alternative: 'For simple concatenation without positioning, merge_mesh_files also works.' This gives clear guidance on when to use this tool versus a sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server