Skip to main content
Glama

add_mesh_fillet

Rounds sharp edges on STL meshes to reduce stress risers and improve print success. Set fillet radius and angle threshold.

Instructions

Add fillets (rounded transitions) at sharp edges.

        Detects edges where adjacent faces meet at a sharp angle and
        inserts intermediate triangles to approximate a smooth fillet.
        Reduces stress concentration at corners and improves printability.

        Use after ``design_scorecard()`` flags sharp corners or
        ``predict_print_failures()`` detects stress risers.

        :param file_path: Path to the STL file.
        :param radius_mm: Fillet radius in mm (default 1.0).
        :param angle_threshold_deg: Edges sharper than this get filleted (default 60).
        :param output_path: Output path (defaults to ``<name>_filleted.stl``).
        :returns: Dict with sharp edge count, triangles added, and output path.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
radius_mmNo
output_pathNo
angle_threshold_degNo
Behavior4/5

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

No annotations provided, so description shoulders full burden. It explains edge detection, triangle insertion, stress reduction, and printability improvement. Describes parameters and return values, but could be more explicit about file handling (e.g., whether original file is modified).

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?

Well-structured: first line defines purpose, then behavior, then usage hint, then parameter list. Slightly wordy but not excessive. Each sentence adds value; could trim redundancy but overall effective.

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?

Given 4 parameters, no output schema, and no annotations, the description provides sufficient context to understand tool usage, parameter meanings, return value, and typical application. Lacks error handling or edge case mentions, but adequate for a mesh manipulation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage; description compensates by explaining each parameter: file_path, radius_mm, angle_threshold_deg, output_path, including defaults and behavior of angle_threshold_deg. Output path default is clearly stated.

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?

Description clearly states "Add fillets (rounded transitions) at sharp edges" with specific verb (Add) and resource (mesh fillet). It explains the detection and smoothing process, distinguishing from sibling add_mesh_chamfer by specifying rounded transitions vs flat bevels.

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?

Explicitly advises using after design_scorecard() flags sharp corners or predict_print_failures() detects stress risers, providing clear when-to-use context. Does not explicitly state when not to use or alternative tools, but the guidance is sufficient for most use cases.

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

Install Server

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