Skip to main content
Glama
solidworks-mcp

solidworks-mcp

insert_component

Insert a part or sub-assembly file into the active assembly at specified X, Y, Z coordinates in millimeters, with the component's origin placed at that point and no rotation applied.

Instructions

Inserts a part or sub-assembly (a .SLDPRT / .SLDASM file, relative to the projects folder when one is set) into the active assembly, with the component's origin at (x, y, z) mm and no rotation. The file is opened in the background if it is not already open, and its window is closed again afterwards.

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": "<path>"
    },
    "name": "insert_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
x_mmNo
y_mmNo
z_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses real side effects — the file is opened in the background if not already open and its window is closed afterwards — plus the exact placement rule (origin at the target coordinate, no rotation applied). This is meaningful context the agent could not infer from readOnlyHint=false / destructiveHint=false alone; repeat-call behavior (duplicate instances) is implied but not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and the placement rule, then the background open/close side effect. No filler and no restatement of the tool name.

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?

The output schema means return values need no explanation, and the description covers the required precondition, path resolution, units, and document side effects. Missing only error behavior for a nonexistent or unsupported file.

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 0%, so the description has to carry the parameters, and it does: path is explained in terms of accepted file types and the projects-folder base, and x/y/z are explained as the component origin in millimeters with no rotation. The default (0,0,0) and what happens on an unresolvable path are not covered, keeping it below full marks.

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 description gives a specific verb (inserts) and resource (a part or sub-assembly, .SLDPRT/.SLDASM) with the resulting placement (origin at x,y,z mm, no rotation). That is enough to distinguish it from siblings like insert_model_dimensions or add_mate without opening the schema.

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?

It establishes the operating context: an active assembly must exist, and paths resolve relative to the projects folder when one is set. It doesn't name exclusions or alternatives, but no sibling clearly competes for this action, so the missing piece is minor.

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