Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

simplify_mesh_model

Reduce STL mesh triangle count with vertex-clustering decimation to produce a lower-resolution version for faster previews or smaller files.

Instructions

Reduce mesh triangle count for faster preview or smaller files.

        Uses vertex-clustering decimation to merge nearby vertices.
        The result is a lower-resolution version of the same shape.

        :param file_path: Path to the STL file.
        :param target_ratio: Target fraction of original triangles (0.01-1.0).
        :param output_path: Output path (defaults to ``<name>_simplified.stl``).
        :returns: Dict with original/simplified triangle counts and reduction percentage.

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": "simplify_mesh_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the STL file.
output_pathNoOutput path (defaults to ``<name>_simplified.stl``). Default: "".
target_ratioNoTarget fraction of original triangles (0.01-1.0). Default: 0.5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • 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 ``<name>_simplified.stl``). Default: \"\"."
    • changedInput schema / properties / target_ratio / description
      Previous value: -"Default: 0.5."New value: +"Target fraction of original triangles (0.01-1.0). Default: 0.5."
  2. Changed4 schema fields changedv1.5.0
    • removedInput schema / properties / output_path / default
      Removed value: -""
    • addedInput schema / properties / output_path / description
      Added value: +"Default: \"\"."
    • removedInput schema / properties / target_ratio / default
      Removed value: -0.5
    • addedInput schema / properties / target_ratio / description
      Added value: +"Default: 0.5."
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: it discloses that a new STL is written with a default derived filename, that the operation is lossy shape reduction, what the return dict contains, and — most valuably — that success opens an interactive 3D stage in supporting hosts with automatic decimation for oversized meshes. It does not say whether an existing output file is overwritten or whether the source file is touched.

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 and mechanism are front-loaded and the UI-stage note is separated into its own paragraph. The Sphinx-style ':param:' blocks duplicate the JSON schema word-for-word, which is wasted space in an agent-facing description.

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?

With no output schema, the description supplies the return shape (original/simplified counts, reduction percentage) and the default output filename, so an agent knows what it gets back and where. The remaining gap is side-effect/persistence semantics — overwrite behavior and whether the input mesh is preserved — which matter for a file-writing tool.

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 every parameter is already documented; the ':param' lines largely restate the same text (file_path is verbatim identical). The only subtle addition is framing target_ratio as a fraction of original triangles, which the schema already conveys. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb and resource ('Reduce mesh triangle count') plus the mechanism ('vertex-clustering decimation') and the nature of the output ('lower-resolution version of the same shape'). This implicitly separates it from siblings like rescale_model, thicken_mesh_walls or hollow_mesh_model, though it never names an alternative explicitly.

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?

Gives clear when-to-use motivation ('faster preview or smaller files'), which is enough context to select it over unrelated mesh tools. It offers no when-not guidance, no prerequisites (e.g. mesh must be watertight/manifold), and no named alternative for cases where decimation is the wrong approach.

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