Skip to main content
Glama

thicken_mesh_walls

Fix thin walls in a mesh by offsetting vertices outward. Detects weak regions and thickens the geometry, outputting a corrected STL after print-failure analysis flags them.

Instructions

Thicken thin walls in a mesh by offsetting vertices outward.

        Detects thin-wall regions and pushes vertices outward along their
        averaged normals.  This is a **geometry-level fix** -- the mesh is
        surgically modified instead of regenerating from scratch.

        Use after ``predict_print_failures()`` detects ``thin_walls`` or
        after ``design_scorecard()`` flags wall thickness issues.

        :param file_path: Path to the STL file.
        :param amount_mm: Offset distance in mm (default 0.5).
        :param output_path: Output path (defaults to ``<name>_thickened.stl``).
        :returns: Dict with number of vertices modified, amounts, 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
amount_mmNo
file_pathYes
output_pathNo
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses geometry-level modification, vertex offsetting along averaged normals, automatic decimation for the viewer, and the inline 3D stage side effect. It does not explicitly state whether the original STL file is left untouched, though the output_path default implies a new file is written.

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 description is front-loaded with a one-sentence purpose, followed by concise method, usage, parameter, and return details. The inline 3D stage block is long but earns its place as important behavioral context. It is slightly verbose in the stage explanation but remains well structured.

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 annotations and no output schema, the description robustly covers params, return values, usage timing, and side effects. It is strong for a geometry-editing tool, but minor gaps remain around input file preservation and failure/error behavior.

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?

The schema has 0% description coverage, but the description fully documents all three parameters: file_path, amount_mm with default and unit, and output_path with default behavior. It also summarizes the return dict contents, adding meaning well beyond the bare input schema.

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 specific verb and resource: 'Thicken thin walls in a mesh by offsetting vertices outward.' This clearly distinguishes it from sibling mesh operations like repair_mesh, hollow_mesh_model, or add_mesh_fillet. The phrase 'geometry-level fix' further reinforces the tool's specific role.

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 explicitly states when to use the tool: 'Use after predict_print_failures() detects thin_walls or after design_scorecard() flags wall thickness issues.' This gives clear context and names upstream tools, though it does not enumerate exclusions or alternatives.

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