Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

sweep

Creates a tube, handle, rail, or wire form by moving a closed sketch profile along a joined path sketch, supporting join, cut, intersect, and new-body operations.

Instructions

Sweep a sketch's closed profile along a path — a tube, handle, rail or wire form. Not sweep_rotation, which swings assembly components to check collisions.

The path is a second sketch whose lines and arcs join end to end (draw_line, draw_arc), on a plane across the profile's — e.g. the path on XZ, the profile on XY where the path starts. Arcs must join the lines tangentially, or the profile kinks and the sweep fails. Returns the feature name and the volume / topology change.

Args: path_sketch: Sketch number holding the path. sketch_index: Sketch number of the profile (0 = latest sketch). operation: "join" (add), "cut", "intersect" or "new" (a separate body). orientation: "normal" (the profile stays square to the path) or "parallel" (it keeps its original direction). taper: Draft angle in degrees; positive grows the profile along the path. twist: Rotation of the profile over the whole path, in degrees.

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": {
      "path_sketch": "<path_sketch>"
    },
    "name": "sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
taperNo
twistNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
operationNojoin
orientationNonormal
path_sketchYes
sketch_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.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 full burden and does well: it discloses the dominant failure mode (kinked profile causes sweep failure), the plane-relationship requirement, and what is returned (feature name plus volume/topology change). It does not say whether the operation mutates or creates a document, nor anything about the disconnected-instance case, which are the main remaining gaps for a mutation tool.

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 and the sibling exclusion, followed by preconditions, then the args list. Every sentence carries information, though the line-wrapped delivery of the first paragraph is slightly awkward and a couple of the arg glosses could be tightened.

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 7-parameter CAD mutation tool with no annotations, the description supplies the geometry prerequisites, failure conditions, mode semantics, and a return summary (an output schema also exists, so return detail is not required). What is missing is only marginal: how multiple connected instances are chosen and whether the operation alters existing bodies beyond the stated operation modes.

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 description coverage is only 14% (just the instance field), so the description must compensate and largely does: it defines path_sketch, sketch_index (0 = latest sketch), the four operation modes ('join' add, 'cut', 'intersect', 'new' separate body), both orientation modes with their geometric meaning, and the directional sense of taper and twist. The only undocumented parameter is instance, and the units/sign conventions for taper are given while default values are left to the schema.

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?

The first sentence names a specific verb and resource (sweep a sketch's closed profile along a path) and gives concrete exemplar outputs (tube, handle, rail, wire form). It also explicitly excludes the similarly-named sibling sweep_rotation by describing what that tool does instead.

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?

It states the geometric preconditions for use: the path must be a second sketch of end-to-end lines/arcs on a plane crossing the profile's plane, and arcs must be tangent or the sweep fails. The exclusion of sweep_rotation is explicit, so an agent can route correctly without opening another schema.

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