Skip to main content
Glama
effectustasi

autodesk-inventor-mcp

by effectustasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find the smallest faces

smallest_faces
Read-onlyIdempotent

List N faces sorted by area ascending to detect sliver or near-zero-area import defects in STEP/IGES models. Returns face indices, areas, edge counts, and centers.

Instructions

Lists the N smallest faces of a body, sorted by area ascending. Each entry has the 1-based face index, area in mm^2, edge count, surface type and center point in mm. Also returns the body's total face count and total area. Use it to find import defects such as sliver or near-zero-area faces from STEP/IGES files; the returned indices work with face_neighbors and unwrap_try.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo1-based index of the solid/surface body in the part, as listed by `model_info`. Most parts have one body.
countNoHow many of the smallest faces to return.
documentNoDisplay name of an open document, as listed by `status` (e.g. "Bracket.ipt"). Omit or leave empty to use the active document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • addedInput schema / properties / body / description
      Added value: +"1-based index of the solid/surface body in the part, as listed by `model_info`. Most parts have one body."
    • addedInput schema / properties / body / minimum
      Added value: +1
    • addedInput schema / properties / count / description
      Added value: +"How many of the smallest faces to return."
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / document / description
      Added value: +"Display name of an open document, as listed by `status` (e.g. \"Bracket.ipt\"). Omit or leave empty to use the active document."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds ordering guarantees (area ascending) and the exact return payload, which matters because no output schema exists. It does not mention cost, limits, or behavior on bodies with fewer than N faces.

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?

Two sentences, no filler, and the core behavior (what is listed, in what order, with what fields) is front-loaded before the use case. Every clause carries information an agent needs.

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?

With no output schema, the description fully compensates by enumerating the returned fields (index, area in mm^2, edge count, surface type, center) and the aggregate totals. Combined with complete schema coverage, nothing needed to call or interpret the tool is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so 'body', 'count' and 'document' are already documented in the schema. The description only restates 'N smallest faces' and never mentions the document parameter or the 1-based body indexing, so it adds little beyond the structured fields — the baseline 3 applies.

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 ('Lists the N smallest faces of a body') plus the sort order, and the return-field enumeration makes the operation unambiguous. An agent can distinguish it from siblings like face_neighbors or model_info without opening any schema.

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 names the motivating scenario (finding sliver or near-zero-area import defects from STEP/IGES) and points to the downstream tools the returned indices feed into. It stops short of saying when not to use it or what alternative to prefer for other diagnostic needs, so it is clear context rather than full routing guidance.

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

Deploy Server

Other Tools