Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

hollow_mesh_model

Create a hollow version of an STL mesh by generating an inner offset shell, reducing material use while reporting estimated savings.

Instructions

Create a hollow version of a mesh to save material.

        Generates an inner offset shell and combines it with the outer
        surface.  Reports estimated material savings.

        :param file_path: Path to the STL file.
        :param wall_thickness_mm: Wall thickness in mm (default 2.0).
        :param output_path: Output path (defaults to ``<name>_hollow.stl``).
        :returns: Dict with hollowing stats and material savings.

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

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the STL file.
output_pathNoOutput path (defaults to ``<name>_hollow.stl``). Default: "".
wall_thickness_mmNoWall thickness in mm (default 2.0). Default: 2.0.

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>_hollow.stl``). Default: \"\"."
    • changedInput schema / properties / wall_thickness_mm / description
      Previous value: -"Default: 2.0."New value: +"Wall thickness in mm (default 2.0). Default: 2.0."
  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 / wall_thickness_mm / default
      Removed value: -2
    • addedInput schema / properties / wall_thickness_mm / description
      Added value: +"Default: 2.0."
  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 only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description carries the rest and does so well: it discloses the internal offset-shell construction, that material savings are estimated and reported in the return dict, that oversized meshes are auto-decimated for the stage, and that a 3D viewer panel opens on success. The main omission is whether an existing output_path is overwritten, which matters for a file-writing tool.

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 opening two sentences are front-loaded and efficient, and the stage paragraph conveys genuinely useful expectations. However, the ':param' block is pure duplication of structured schema fields and the ':returns:' note restates what the prose already said about reporting savings, so a meaningful fraction of the text does not earn its place.

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 correctly compensates by describing the return shape ('Dict with hollowing stats and material savings'). All three parameters are documented and the side effect of opening an inline viewer is disclosed. It falls short only on overwrite semantics and any mesh-validity prerequisites for a file-producing mutation.

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%, and the ':param' lines in the description are near-verbatim copies of the schema text (path to STL, wall thickness default 2.0, output path default). No additional meaning — units constraints, valid ranges for wall thickness, or behavior when output_path exists — is added beyond the schema, so baseline 3 applies.

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?

The description names a specific verb and resource ('Create a hollow version of a mesh') and explains the mechanism ('Generates an inner offset shell and combines it with the outer surface'), which is far more informative than the bare name. It does not, however, distinguish itself from adjacent mesh-editing siblings such as thicken_mesh_walls or simplify_mesh_model, leaving the agent to infer the boundary.

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?

The only usage cue is the goal phrase 'to save material'. There is no statement of when this tool is preferred over alternatives, no preconditions (e.g. mesh must be watertight/manifold), and no exclusions. The agent must already know it wants hollowing before this description helps.

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