Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

import_step

Imports vendor STEP files into Inventor assemblies in a destination folder, copying the STEP first and returning component bounding boxes to guide mounting and placement.

Instructions

Import a vendor STEP file (hinge, lock, gland...) as Inventor files in dest_folder. The STEP is copied into dest_folder first, because Inventor writes the parts of an imported assembly next to the .step file (e.g. into Downloads or a synced folder). Returns path, type, overall bbox and per-component bbox/volume — use them to find mounting faces and axes before placing it with place_components.

Args: step_path: The downloaded .step / .stp file. dest_folder: Project folder to hold the Inventor files. name: Base name for the .iam/.ipt (default: the STEP file name).

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": {
      "step_path": "<step_path>",
      "dest_folder": "<dest_folder>"
    },
    "name": "import_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
step_pathYes
dest_folderYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.4/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 a real filesystem side effect (the STEP is copied into dest_folder) and explains why (Inventor writes assembly parts next to the .step file), which is non-obvious behavior an agent could not infer. It also summarizes the return payload. It does not state what happens on name collisions or whether existing files get overwritten, which is the remaining gap for a file-creating mutation.

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, then the rationale for the copy, then the downstream use of the return values, then a clean Args block. Every sentence carries information; the only mild redundancy is restating name's default in the Args block, which the schema title already implies.

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 4-parameter mutation with an output schema already documenting return structure, this description covers action, side effects, rationale, output summary, and downstream handoff. Nothing an agent needs in order to call it correctly and use the result is missing.

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 25%, so the description must compensate, and it largely does: an Args block documents step_path, dest_folder, and the name default (STEP file name). The fourth parameter, instance, is omitted from the description but is the one parameter the schema itself documents (pointing at list_instances), so coverage is effectively complete.

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: import a vendor STEP file and produce Inventor files in a destination folder. It is clearly distinguishable from siblings like load_library (library parts), place_components (assembly placement), and create_document (empty docs). The parenthetical examples of vendor parts add a concrete sense of scope.

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?

Explicitly routes the agent forward: use the returned bbox data to find mounting faces and axes *before* placing with place_components, which names the sibling and the ordering constraint. There are no explicit when-not-to-use conditions or prerequisites (e.g. Inventor connectivity, licensing), so it stops short of a 5.

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