Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

mirror_mesh_model

Destructive

Reflects an STL mesh across the X, Y, or Z axis, reversing triangle winding to keep normals correct. Saves to a chosen output path or overwrites the input file.

Instructions

Mirror (reflect) a mesh along an axis.

        Creates a mirror image by negating coordinates on the chosen axis
        and reversing triangle winding order to preserve correct normals.

        :param file_path: Path to the STL file.
        :param axis: Axis to mirror ("x", "y", or "z", default "x").
        :param output_path: Output path (defaults to overwriting input).
        :returns: Dict with mirror info.

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_path": "<file_path>"
    },
    "name": "mirror_mesh_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNoAxis to mirror ("x", "y", or "z", default "x"). Default: "x".
file_pathYesPath to the STL file.
output_pathNoOutput path (defaults to overwriting input). Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / axis / description
      Previous value: -"Default: \"x\"."New value: +"Axis to mirror (\"x\", \"y\", or \"z\", default \"x\"). Default: \"x\"."
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the STL file."
    • changedInput schema / properties / output_path / description
      Previous value: -"Default: \"\"."New value: +"Output path (defaults to overwriting input). Default: \"\"."
  2. Changed4 schema fields changedv1.5.0
    • removedInput schema / properties / axis / default
      Removed value: -"x"
    • addedInput schema / properties / axis / description
      Added value: +"Default: \"x\"."
    • removedInput schema / properties / output_path / default
      Removed value: -""
    • addedInput schema / properties / output_path / description
      Added value: +"Default: \"\"."
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: the default behavior overwrites the input file, normals are preserved by reversing winding order, oversized meshes are auto-decimated for the stage, and the interactive 3D stage panel is opened on success. It does not, however, warn about failure modes or what happens when the STL is non-manifold.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded and clear, but the raw Sphinx :param:/:returns: block duplicates the input schema verbatim, and the trailing stage paragraph is long relative to the operation described. Roughly a third of the text could be removed with no loss for an agent that already sees the schema.

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 three-parameter mesh mutation with no output schema, the description covers the transformation semantics, the destructive default (overwriting the input), the return type, and the side effect of opening a viewer panel. The main remaining gap is the absence of guidance on related mesh operations, which a sibling-heavy toolset like this one makes more important.

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%, so the parameter list in the description largely restates the schema (file_path, axis values, output_path default). The value it adds is conceptual — that axis selects which coordinate sign is flipped — but no format, range, or edge-case detail beyond the schema is provided.

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

Purpose4/5

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

States a specific verb and resource ("Mirror (reflect) a mesh along an axis") and even explains the mechanism: negating coordinates on the chosen axis and reversing triangle winding. It never names or contrasts with related siblings like rotate_model, rescale_model, or boolean_mesh_op, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives (e.g., rotate_model for orientation, merge_mesh_files for combining). The only usage-adjacent signal is the note that output_path defaults to overwriting the input, which is behavioral rather than routing guidance.

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