Skip to main content
Glama
effectustasi

autodesk-inventor-mcp

by effectustasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Faces adjacent to a face

face_neighbors
Read-onlyIdempotent

Returns a face and all edge-adjacent faces with index, area, edge count, surface type and center point, sorted by area, to inspect suspicious small faces before fixing or excluding them.

Instructions

Returns the given face and every face that shares an edge with it, each with index, area in mm^2, edge count, surface type and center point in mm; neighbors are sorted by area, largest first. Use it to see what a suspicious small face sits between before excluding or fixing it.

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.
indexYes1-based index of the face to inspect, e.g. from smallest_faces.
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 / 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."
    • changedInput schema / properties / index / description
      Previous value: -"1-based face index"New value: +"1-based index of the face to inspect, e.g. from smallest_faces."
    • addedInput schema / properties / index / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds useful behavior beyond that: the result includes the input face itself and neighbors, and neighbors are sorted by area descending, which is not in the schema or annotations.

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?

Two sentences, front-loaded with the return contents and sorted order, followed by the intended use. No filler, though the field enumeration makes the first sentence dense.

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 read-only, three-param inspection tool with no output schema, the description covers return contents, sort order, and intended use. It is nearly complete; only the absence of explicit ordering rationale or edge-case behavior (e.g., boundary faces with no neighbors) keeps it from a 5.

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 coverage is 100%, so all three parameters (body, index, document) are already described, and the description adds no syntax or format detail beyond what the schema provides. The organic connection to smallest_faces in the schema description is echoed here but adds little new. Baseline 3 is appropriate when the schema does the heavy lifting.

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: returns the given face plus every edge-adjacent face, with an explicit field list (index, area mm^2, edge count, surface type, center point mm). This is far more than a name restatement and an agent can identify the operation's scope immediately.

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?

Gives a clear use case: 'Use it to see what a suspicious small face sits between before excluding or fixing it,' which ties it to smallest_faces via the index param. It stops short of naming explicit when-not-to-use conditions or a true alternative sibling, so it's clear context without exclusions.

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