Skip to main content
Glama

analyze_non_manifold_edges

Diagnose non-manifold edges in a 3D mesh by counting boundary, T-junction, and manifold edges to pinpoint problematic areas before repair.

Instructions

Count and classify non-manifold edges in a mesh.

        Reports boundary edges (shared by 1 triangle), T-junction edges
        (shared by 3+ triangles), and manifold edges (shared by exactly 2).

        This is the diagnostic version of the manifold check -- use it
        to understand exactly how many edges are problematic before
        deciding whether to repair.

        :param file_path: Path to mesh file (.stl, .obj, or .glb).
        :returns: Dict with edge count breakdown and watertight status.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
Behavior4/5

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

With no annotations, the description carries full burden. It states the tool is diagnostic and reports results without side effects, and describes the return value (dict with edge count and watertight status). This adequately discloses its read-only nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, well-structured, and front-loaded with the main action. It uses line breaks for readability without unnecessary words, earning its place with every sentence.

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?

For a simple tool with one parameter and no output schema, the description is fairly complete: it explains the function, return type, and file format. It does not detail the dict structure, but the summary is adequate for an agent to invoke and interpret results.

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?

The only parameter file_path has 0% schema description coverage, but the tool description adds value by specifying supported formats (.stl, .obj, .glb). This compensates for the schema gap, though it could include path type hints.

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 clearly states the tool counts and classifies non-manifold edges into specific categories (boundary, T-junction, manifold). It distinguishes itself as the diagnostic version before repair, making the purpose specific and distinct from sibling tools.

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 advises using this tool 'to understand exactly how many edges are problematic before deciding whether to repair,' providing clear context for when to use it. It does not explicitly name alternative tools for repair but implies the diagnostic role, which is sufficient.

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