Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_drawing

Create a new SolidWorks drawing document from a specified template or the default, with optional source model and sheet format, and make it the active document.

Instructions

Create a new SolidWorks drawing document.

This tool creates a new drawing document from template (a .drwdot path) or, without one, the default drawing template. The new drawing will become the active document.

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

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: -"Drawing template file path"New value: +"Drawing template (.drwdot) path; omit to use the SolidWorks default"
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose two genuinely useful behaviors: the template fallback to the SolidWorks default, and the side effect that the new drawing becomes the active document. It does not say what happens to the previously active document, whether an existing name collides or errors, where the file is written, or whether it is saved to disk at all.

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?

Two tight sentences, front-loaded with the core action, and no filler. Minor redundancy between 'Create a new SolidWorks drawing document' and 'This tool creates a new drawing document from...' but it is not wasteful enough to penalize further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and parameter documentation is complete, so return values and inputs are covered. What remains thin is the surrounding context for a creation tool with zero annotations: session prerequisites, file-location/save semantics, and behavior on name collisions are all absent.

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 each nested property is already documented; the description only restates the template semantics. It adds nothing about model_path or sheet_format, and nothing about what 'name' actually controls (document title vs. filename). Baseline 3 applies when the schema does the explaining.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 SolidWorks drawing document') and clarifies it is a whole document, not a view, which meaningfully separates it from siblings like create_drawing_view, add_drawing_view and create_technical_drawing. It never names those siblings explicitly, so the differentiation is inferential rather than stated.

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

Usage Guidelines2/5

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

The text explains how the template parameter resolves but never says when to reach for this tool versus create_part/create_assembly/create_technical_drawing, nor any prerequisites (SolidWorks session running, existing document state). An agent must infer the usage scenario from the verb alone.

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