Skip to main content
Glama

splice_mesh_at_z

Combine an STL's geometry above a Z-plane with another's below, clipping boundary triangles cleanly to create a new mesh for design iteration.

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.

INLINE 3D STAGE: on success this tool also 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
z_planeYes
top_pathYes
bottom_pathYes
output_pathNo
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description fully carries behavioral disclosure. It explains the top/bottom geometry selection, clean clipping of crossing triangles, non-boolean behavior, auto-generated output path, returned dictionary content, inline 3D stage behavior, oversized-mesh decimation, and preview limitations. This is rich, specific behavioral context beyond the schema.

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 uses short labeled sections and every sentence adds distinct value: what the tool does, how clipping works, use case, parameter definitions, return contract, and the 3D stage behavior. It is thorough without being bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete: it documents all four parameters, return value shape, non-manifold support, clipping behavior, and the side-effect of opening the interactive 3D stage. Since no output schema exists, including the return dictionary and stage behavior is essential and well-handled.

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?

Schema description coverage is 0%, and the description fully compensates by documenting every parameter: top_path, bottom_path, z_plane (with mm unit), and output_path (with auto-generation semantics). This adds meaning far beyond the schema's bare titles like 'Top Path' and 'Z Plane'.

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 opens with a precise action and resource: 'Splice two meshes at a z-plane', then clarifies top from one STL and bottom from another. It distinguishes from sibling tools like boolean_mesh_op and merge_stl by explicitly stating 'No boolean ops' and 'works on non-manifold meshes', making the tool's unique role clear.

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 provides a concrete named use case: combine a body with the correct top (logo from v5.3) with one having the correct bottom (larger pocket from v5.4). It also implies when NOT to use boolean alternatives with 'No boolean ops -- works on non-manifold meshes', but it doesn't name alternative tools explicitly.

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

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