Skip to main content
Glama

analyze_mesh_geometry

Analyze 3D mesh geometry to compute volume, surface area, overhangs, and printability score, identifying issues before slicing.

Instructions

Deep geometric and printability analysis of a 3D mesh.

        Goes beyond basic validation to compute volume, surface area,
        center of mass, overhang detection, connected components (floating
        parts), degenerate triangles, and a composite printability score
        (0-100).

        Use this after generating a model to understand its geometry and
        identify printability issues before sending to the slicer.

        :param file_path: Path to .stl, .obj, or .glb file.  For a
            STEP/STP CAD file, convert it first with ``import_step_file``
            and analyze the resulting mesh.
        :returns: Dict with full mesh analysis metrics.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
Behavior3/5

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

No annotations provided, so description carries burden. Implies read-only analysis but does not explicitly state safety, error cases, or performance implications. Lists computed metrics but not side effects.

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 with purpose, list, usage context, and parameter note. Slightly lengthy but remains focused and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description only vaguely mentions returns a dict with metrics. Does not structure the output keys or specify error conditions, leaving agents to guess the return format.

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?

Only one parameter (file_path), and description thoroughly explains accepted formats (.stl, .obj, .glb) and provides guidance for STEP files. Schema description coverage is 0%, so description compensates excellently.

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?

Clearly states deep geometric and printability analysis, lists specific metrics (volume, surface area, etc.), and specifies it's for 3D meshes after generation. However, sibling tools like 'validate_and_prepare_mesh' and 'analyze_printability' exist without explicit differentiation.

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 says use after model generation before slicing, and gives a note about STEP file conversion. Does not mention when not to use it or alternative tools, but context is clear.

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