Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Assembly

create_assembly

Creates a new empty SolidWorks assembly document and makes it active, ready for inserting components; accepts an optional .asmdot template and requires SolidWorks running.

Instructions

Create a new, empty assembly document and make it active, ready for insert_component.

Uses template (an .asmdot) or the default assembly template. It is not saved until save_file. Needs: SolidWorks running. Changes: opens a new assembly document. Returns: assembly with name and template. Then call insert_component for each part.

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": {
      "input_data": "<input_data>"
    },
    "name": "create_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe assembly. `name` is required but only a label: the reply gives SolidWorks' own name (Assem1, ...); `template` has a default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false), and the description goes beyond them by disclosing the external dependency ('Needs: SolidWorks running'), the side effect ('opens a new assembly document'), the persistence gap until save_file, and the return payload. This is the kind of context annotations cannot carry.

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 action, then a compact Needs/Changes/Returns/Next block that is easy to scan. Slightly redundant in mentioning `insert_component` in both the first sentence and the closing line, but no sentence is wasteful.

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?

An output schema exists, and the description still names the return shape (`assembly` with `name` and `template`), while covering preconditions, side effects, and follow-up steps. Nothing material is missing for a one-parameter creation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3: `name` as a label and `template` as an optional .asmdot path are already documented in the schema. The description only restates that `template` defaults to the SolidWorks template, adding no syntax or format detail beyond structured fields.

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 ('Create a new, empty assembly document') plus the resulting state ('make it active'), and ties it to the next step in the workflow via `insert_component`. An agent can distinguish it from create_part or load_assembly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing guidance: call this first, then 'call `insert_component` for each part', and the precondition that the result 'is not saved until `save_file`'. The alternative (using a provided template vs the default) is also named, so nothing needs to be inferred.

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

Deploy Server

Other Tools