Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

extrude

Turn a sketch's closed profile into 3D by adding material, cutting, intersecting, or creating a new body, with distance, direction, and through-all extent options.

Instructions

Turn a sketch's closed profile into 3D: add material, cut it, or start a new body. For a turned shape use revolve; for sheet metal, add_sheet_metal_face and sheet_metal_cut.

Returns the feature name and the change, e.g. "V 23497 (-503 mm³) | F7 E14": read it — a cut showing no volume change went the wrong way or missed the body; try the other direction. Without a closed profile it fails and says where the gap is (as check_sketch does).

Args: distance: mm. Ignored when extent_type="all". direction: "positive" (along the sketch normal: +Z on the XY plane), "negative" or "symmetric". operation: "join" (add), "cut", "intersect", "surface" or "new" (a separate body). sketch_index: Sketch number (0 = latest sketch). extent_type: "distance", or "all" to go through the entire body.

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": "extrude"
  }
}

Input Schema

NameRequiredDescriptionDefault
distanceNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
directionNopositive
operationNojoin
extent_typeNodistance
sketch_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the failure mode (no closed profile → fails and reports the gap, as check_sketch does), the return string format with a concrete example, and how to read that return value to detect a misdirected cut.

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 purpose, then routing, then the return-string contract, then parameters — a sensible order with no filler sentences. The Args list slightly overlaps the prose ('add material, cut it' vs operation values), but every entry adds enum detail the schema lacks.

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 mutation tool with zero annotations and a thin schema, everything needed is present: purpose, alternatives, failure behavior, parameter values, and how to interpret the returned change string. The output schema exists, but explaining how to read 'V 23497 (-503 mm³) | F7 E14' adds genuine diagnostic value rather than just restating a return type.

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

Parameters4/5

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

Schema coverage is only 17%, so the Args block is doing real work: it enumerates operation values (join/cut/intersect/surface/new), direction values with the +Z-on-XY-plane meaning, sketch_index's 0 = latest convention, and the distance/extent_type interaction. Only 'instance' is skipped, but that one already has a schema description, so the gap is minor.

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 ('Turn a sketch's closed profile into 3D') and immediately scopes it against the adjacent operations: revolve for turned shapes, add_sheet_metal_face/sheet_metal_cut for sheet metal. An agent can pick it out from siblings like revolve and sweep_rotation without opening a schema.

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?

Explicitly names alternatives and the condition that selects them ('for a turned shape use revolve; for sheet metal...'), and adds a recovery guideline: a cut with no volume change went the wrong way, try the other direction. That is both when-to-use and what-to-do-on-failure.

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