Skip to main content
Glama

Find holes and faces of an STL

find_features
Read-onlyIdempotent

Lists cylindrical holes, bosses, and flat faces in an STL file with dimensions in mm, so you can inspect part features before topology optimization.

Instructions

List the holes, bosses and flat faces of an STL file, in mm. Read only: the file is read and nothing is written (CONTRACTS.md section 45).

stl_path: an STL file (a relative path starts at the work folder). About 4 s for a million triangles. A wrong input gives {"ok": false, "error": ...}. A hole's point, axis, radius_mm and length_mm are the keys of a bore in interfaces (section 23). holes: each cylindrical hole has id, point (the centre of the first end face), the unit axis, radius_mm, length_mm, end_point, depth (through, blind, closed or unknown), ends, arc_deg (the angle the wall covers), segments and chord_sag_mm (the facets lie that far inside the radius), fit (distance of the wall vertices to the circle) and coaxial_with (a stepped hole is two cylinders on one axis). Every hole is listed with its radius and fit, whatever its size. bosses: convex cylinders (a shaft, a post), the same keys without depth. flat_faces: planar regions, the largest first: normal (outward, unit), area_mm2, centroid, offset_mm. mesh: faces, watertight, bounds_mm. A mesh that is not closed still gives what can be found (no repair). method: numbers (each detection number as used) and counts. facts: plain sentences (an open mesh, a stepped hole, a feature near a limit, regions left out). A hole whose wall joins a fillet, a tapered hole and a slot are not cylinders to this method. Your STL as a region item of build_regions: {stl: {path: part.stl, plug_holes: [H1] or all, screw_holes: [H2] or all, ring_mm: 2}} (a relative path starts at the work folder; a growth box is one more item). Only a closed solid mesh is read (no repair). plug_holes fills those holes (ids stable for one file). screw_holes adds a frozen ring round each: t = 0.5 x d, at least 2 voxels, or ring_mm (a number, or {H2: 2}). {screw_ring: {path: part.stl, hole: H2}} is that ring as a fixed or load region. A mouth chamfer and a drill point stay.

Input Schema

NameRequiredDescriptionDefault
stl_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by detailing return structure (holes, bosses, flat_faces, mesh, method, facts), timing, error format, limitations (open mesh still returns what can be found, no repair), and the exact integration with build_regions. This is rich behavioral context that helps an agent understand what to expect.

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 description is a long, dense block of text with many technical details and references to external documentation (CONTRACTS.md sections). While the information is useful, it is not front-loaded or well-segmented, making it harder to scan quickly.

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

Completeness5/5

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

Given the complexity of the output and the absence of an output schema, the description thoroughly explains all return fields, error behavior, and usage in downstream tools. It leaves little ambiguity about what the tool does and how to interpret its 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 single parameter stl_path has no schema description, but the description compensates by explaining that a relative path starts at the work folder and that it must be an STL file. This is sufficient for a 1-param tool, though not extensive enough for a 5.

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?

States a specific verb and resource: 'List the holes, bosses and flat faces of an STL file'. This clearly distinguishes it from all sibling tools, which deal with runs, regions, materials, etc., not feature extraction from an STL.

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?

Provides clear context: it is read-only, mentions the time cost for a million triangles, describes error behavior, and explains how the output is used with build_regions. It also notes limitations (fillet-joined, tapered holes, slots are not detected) but does not explicitly state when to prefer it over alternatives—though none exist among siblings.

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