Skip to main content
Glama

splice_mesh_at_z

Combine the top geometry from one STL with the bottom geometry from another STL at a specified z-plane, creating a hybrid mesh without boolean operations.

Instructions

Splice two meshes at a z-plane: top from one STL, bottom from another.

        Takes geometry ABOVE *z_plane* from *top_path* and geometry BELOW
        *z_plane* from *bottom_path*.  Triangles crossing the boundary are
        clipped cleanly.  No boolean ops -- works on non-manifold meshes.

        **Use case:** Combine a body with the correct top (e.g. logo from
        v5.3) with a body that has the correct bottom (e.g. larger pocket
        from v5.4) to create the next design iteration.

        :param top_path: STL providing geometry above z_plane.
        :param bottom_path: STL providing geometry below z_plane.
        :param z_plane: Z height (mm) where the splice happens.
        :param output_path: Output STL path. Auto-generated if empty.
        :returns: Dict with splice stats and output path.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
z_planeYes
top_pathYes
bottom_pathYes
output_pathNo
Behavior4/5

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

With no annotations provided, the description carries full burden. It clearly explains the tool takes geometry above/below a z-plane, clips crossing triangles cleanly, works on non-manifold meshes, and returns a dict with stats and output path. Missing details on error handling or file format requirements.

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 well-structured: a concise one-sentence purpose, bullet-point style behavior explanation, use case paragraph, and parameter list. No wasted words, all content is relevant and clearly organized.

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 adequately states return value (dict with splice stats and output path). It explains the algorithm and constraints. Could mention potential error cases or file format requirements, but the tool is sufficiently described for an agent to use correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It provides reST-style parameter documentation: top_path (STL providing geometry above), bottom_path (STL providing geometry below), z_plane (Z height in mm), output_path (Output STL path, auto-generated if empty). This adds significant meaning beyond the schema's types and titles.

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 explicitly states 'Splice two meshes at a z-plane: top from one STL, bottom from another', providing a specific verb and resource. It distinguishes itself from sibling tools like merge_mesh_files by highlighting it works on non-manifold meshes and uses no boolean operations.

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

Usage Guidelines4/5

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

The description includes a 'Use case' paragraph that gives a concrete scenario for when to use this tool. However, it does not explicitly mention when not to use it or name alternatives, though the sibling list provides context.

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