Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_part

Creates a new SolidWorks part document from a .prtdot template or the default template and makes it the active document ready for modeling.

Instructions

Create a new SolidWorks part document.

Creates a new SolidWorks part document from template (a .prtdot path) or, without one, the default part template. The new part becomes the active document and is ready for modeling operations such as sketch creation and feature addition.

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 input data value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / input_data / properties / template / description
      Previous value: -"Template file path for the new part"New value: +"Part template (.prtdot) path; omit to use the SolidWorks default"
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully states that the new part becomes the active document and is ready for modeling, and that template omission falls back to the SolidWorks default, but it does not describe persistence behavior, naming conflicts, permissions, or error conditions.

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?

The description is short and front-loaded with the core action. It has slight redundancy between the first sentence and the opening of the second sentence, but no significant waste.

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 simple document-creation tool with a rich schema and an output schema, the description covers the essential behavior: template source, default fallback, and that the created part becomes active. It could do more on file persistence and failure modes, but the key invocation context is present.

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 schema already documents name, units, material, and template. The description adds some context for the template parameter, including the .prtdot format and default fallback, but it does not explain the other nested parameters beyond what the schema provides.

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 states a specific verb and resource: 'Create a new SolidWorks part document.' It also clarifies that the part can come from a template or the default template, which distinguishes it from sibling creation tools like create_assembly and create_drawing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies this tool is for starting a new part document, especially before modeling operations such as sketching and feature addition. However, it does not explicitly compare against alternatives such as load_part, open_model, or create_assembly, so routing guidance is only implied.

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