Skip to main content
Glama
Sign In
inventor-mcp-server

inventor-mcp-server

by cenitu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_sheet_profile

Creates a complete L, U, C, Z, or hat sheet-metal profile as one contour flange in an empty part from outer width, height, and length; set the sheet-metal rule first for thickness.

Instructions

Make a whole bent profile — angle, channel, Z or hat — as one contour flange in an empty sheet metal part, from outer sizes: section in the XY plane from 0,0, length along +Z. It unfolds like any sheet metal part. Set the rule first (manage_sheet_metal_rules): thickness comes from it. For a panel with walls use add_sheet_metal_face + add_flange.

Args: kind: "L", "U", "C" (U with lips turned in), "Z" or "hat". width: L: bottom leg. U, C: overall width. Z: top flange, measured over the web. Hat: width of the crown. All mm. height: Overall height in mm. length: Length of the profile in mm. flange: C: lip. Z: bottom flange, measured over the web. Hat: each brim. Ignored for L and U. bend_radius: Inside radius in mm; 0 = from the rule.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "width": "<width>",
      "height": "<height>",
      "length": "<length>"
    },
    "name": "add_sheet_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
widthYes
flangeNo
heightYes
lengthYes
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
bend_radiusNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden and does well: it states the resulting geometry orientation, that thickness is inherited from the sheet metal rule, that bend_radius=0 falls back to the rule, and that the result unfolds like any sheet metal part. It stops short of stating failure behavior (e.g. what happens if the part is not empty) or that the operation is a mutation committed to the model, leaving a modest gap.

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-loaded with the core capability before the prerequisite and alternative routing, and the Args block is a clean per-parameter list with no filler. The opening sentence is dense and syntactically tangled, forcing a re-read, which costs it a point but not the structure.

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?

For a 7-parameter, annotation-free CAD mutation with an output schema present, the description supplies prerequisites, geometry orientation, unit conventions, per-kind parameter semantics, and rule inheritance — everything needed to invoke it correctly. Return-value detail is legitimately omitted because an output schema exists.

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

Parameters5/5

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

Schema coverage is only 14%, so the description must compensate, and it does: it defines every profile-relevant parameter and, crucially, supplies the valid `kind` values (L/U/C/Z/hat) that the schema does not enumerate, plus the per-kind meaning of `width` and `flange` and the mm units. The only parameter not covered is `instance`, which the schema already documents.

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?

Specific verb+resource: creates one bent sheet-metal profile (angle, channel, Z, hat) as a single contour flange, with the geometry placement spelled out (XY section from 0,0, length along +Z). It explicitly differentiates itself from the sibling combination add_sheet_metal_face + add_flange, so an agent can choose without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the precondition ('Set the rule first (manage_sheet_metal_rules)'), the environmental constraint ('in an empty sheet metal part'), and the alternative ('For a panel with walls use add_sheet_metal_face + add_flange'). Both when-to-use and when-not-to-use are present.

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