Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

sheet_metal_cut

Cuts holes and rectangular cutouts in a sheet metal panel using a sketch or world-coordinate circles/rectangles; depth follows thickness and verifies material is removed.

Instructions

Cut through a sheet metal panel — depth follows the thickness, so it stays parametric. Checks that material was removed (a cut sketched on a work plane silently removes nothing).

From a sketch on the panel face: one sketch with several closed shapes = several holes. Or at WORLD coordinates, with no sketch axes to think about: face_index + circles / rectangles.

Args: sketch_index: Sketch number (0 = latest). face_index: Face of the sheet (find_faces), for circles / rectangles. circles: [[x, y, z, diameter], ...], e.g. [[180, 267, 0, 4.9]]. rectangles: Lists of 4 corners, [[[x,y,z], [x,y,z], [x,y,z], [x,y,z]], ...].

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sheet_metal_cut"
  }
}

Input Schema

NameRequiredDescriptionDefault
circlesNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
face_indexNo
rectanglesNo
sketch_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / circles
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {},
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Circles"
      +}
    • addedInput schema / properties / face_index
      Added value: +{
      +  "default": 0,
      +  "title": "Face Index",
      +  "type": "integer"
      +}
    • addedInput schema / properties / rectangles
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {},
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Rectangles"
      +}
  2. First observedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious behavior: depth is driven parametrically by thickness, and the tool verifies material was actually removed, warning that a cut sketched on a work plane silently removes nothing. It does not cover failure modes, whether duplicate geometry is tolerated, or any permission/instance implications.

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 action and its parametric behavior before the mode explanation and Args block; every sentence carries information. The Args listing restates some parameter meaning already given in prose, which is mild redundancy rather than waste.

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 5-parameter CAD mutation with an output schema (so return values needn't be explained), the description covers the action, the two invocation modes, the parameter formats, and the verification behavior. The remaining gap — whether sketch_index and face_index are mutually exclusive — is minor.

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 20% and the schema's circles/rectangles items are untyped, so the description compensates well: it documents sketch_index (0 = latest), face_index (with a pointer to find_faces), the [x, y, z, diameter] circle format with an example, and the 4-corner rectangle format. Only `instance` is left to the schema, which already describes it.

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?

Names a specific verb and resource ('Cut through a sheet metal panel') and immediately distinguishes itself from a generic cut/extrude by noting the depth follows the sheet thickness and stays parametric. The two supported input modes (sketch on panel face vs. world coordinates) further pin down what the tool actually does.

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?

Clearly lays out the two ways to drive the cut — a sketch on the panel face (multiple closed shapes = multiple holes) or world coordinates via face_index + circles/rectangles — which is real routing guidance. It stops short of telling the agent when to prefer this over sibling tools like add_hole, draw_slot, or extrude.

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