Skip to main content
Glama
effectustasi

autodesk-inventor-mcp

by effectustasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dry-run an Unwrap

unwrap_try

Attempt Inventor's Unwrap on selected faces to find which set unwraps, reporting success or error, time, face count, area, and bounding box; deletes result by default.

Instructions

Attempts Inventor's Unwrap feature on a set of faces and reports what happened: success or the error and Inventor's last error message, time taken, and on success the result face count, area in mm^2 and bounding box in mm. By default the created feature is deleted right away so the document is left unchanged; pass keep=true to leave it in the model. Use it to find which face set unwraps, which the Inventor UI does not tell you.

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.
keepNoIf true, the Unwrap feature stays in the document (modifies the model). If false (default), it is deleted after measuring.
documentNoDisplay name of an open document, as listed by `status` (e.g. "Bracket.ipt"). Omit or leave empty to use the active document.
alignmentNoPassed to Inventor's Unwrap definition as its alignment option: origin, or the XY/XZ/YZ base plane.origin
face_indicesYes1-based indices of the faces to unwrap, as returned by smallest_faces or face_neighbors.
auto_face_chainNoPassed to Inventor's Unwrap definition as its auto face chain option.
merge_result_bodyNoPassed to Inventor's Unwrap definition as its merge result body option.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.0
    • addedInput schema / properties / alignment / description
      Added value: +"Passed to Inventor's Unwrap definition as its alignment option: origin, or the XY/XZ/YZ base plane."
    • addedInput schema / properties / auto_face_chain / description
      Added value: +"Passed to Inventor's Unwrap definition as its auto face chain option."
    • 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 / face_indices / description
      Previous value: -"1-based face indices"New value: +"1-based indices of the faces to unwrap, as returned by smallest_faces or face_neighbors."
    • addedInput schema / properties / face_indices / items / minimum
      Added value: +1
    • addedInput schema / properties / face_indices / minItems
      Added value: +1
    • changedInput schema / properties / keep / description
      Previous value: -"if true, the created feature stays in the document"New value: +"If true, the Unwrap feature stays in the document (modifies the model). If false (default), it is deleted after measuring."
    • addedInput schema / properties / merge_result_body / description
      Added value: +"Passed to Inventor's Unwrap definition as its merge result body option."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, which alone would be ambiguous for a feature-creating tool. The description resolves this by explaining that the created feature is deleted immediately by default, leaving the document unchanged, and that keep=true modifies the model. It also discloses the returned diagnostics (error, last error message, time, face count, area, bounding box), which the annotations do not.

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?

Front-loads the core action and outcome, then the side-effect semantics, then the motivating use case. Dense but every clause carries information; no filler.

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 compensates by enumerating what is reported on success and failure. Combined with the 100%-covered input schema and the keep semantics, an agent has everything needed to call it correctly and interpret the result.

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 every parameter is already documented in the schema. The description adds meaning only for keep, which the schema already explains, and says nothing about body, alignment, auto_face_chain, or merge_result_body beyond what the schema provides.

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: attempts Inventor's Unwrap on a face set and reports the outcome. This is clearly distinguishable from siblings like status, model_info, smallest_faces, and face_neighbors, which supply indices rather than perform the operation.

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 ('find which face set unwraps, which the Inventor UI does not tell you') and explains the default vs keep=true behavior. It does not name alternative tools or explicitly state when not to use it, but the context is sufficient to select it.

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