Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Part

create_part

Creates and activates a new empty SolidWorks part, applying an optional template, units, and material so you can start sketching.

Instructions

Create a new, empty part document and make it active, ready for create_sketch.

Uses template (a .prtdot) or the default part template, then sets units if given, and assigns material if given. The part is not saved until save_file. Needs: SolidWorks running. Changes: opens a new part document. Returns: part with name, units, template and material (the one assigned, or null), plus a warning when the material couldn't be assigned; the part is created either way.

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_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe part. `name` is required but only a label: the reply gives SolidWorks' own name (Part1, ...); `template`, `units` (mm, cm, m, in, ft) and `material` (a name from `list_available_materials`) are optional.

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?

Beyond the annotations (readOnly=false, idempotent=false, destructive=false) it discloses that a new document is opened as a side effect, that the part is unsaved until `save_file`, and that a material assignment failure returns a `warning` while the part is still created — non-obvious partial-success semantics that an agent needs.

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?

Front-loaded one-line purpose, then labeled Needs/Changes/Returns blocks. No filler; the return-value sentence is dense but each clause carries distinct information.

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?

An output schema exists, yet the description restates the return shape, which is mild duplication but confirms the `warning` field's meaning. For a single-parameter creation tool with a nested input object, preconditions, side effects, and persistence state are all covered — nothing essential 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 100%, so the baseline is 3; the description adds ordering semantics the schema doesn't convey — template first, then units, then material — plus the default-template fallback when `template` is omitted. The warning/null-material relationship adds further meaning.

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?

Specific verb + resource: 'Create a new, empty part document and make it active.' It also states the immediate downstream purpose ('ready for `create_sketch`'), which separates it from `load_part` (existing part) and `create_assembly` (different document type).

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?

Gives clear preconditions ('Needs: SolidWorks running') and lifecycle guidance ('not saved until `save_file`'), and names the follow-on tool `create_sketch`. It stops short of explicitly stating when NOT to use it, e.g. that an existing part should be opened with `load_part` rather than created.

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