Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Drawing

create_drawing

Create and activate a new empty SolidWorks drawing document, using a specified .drwdot template or the default, so you can add views next.

Instructions

Create a new, empty drawing document and make it active.

Uses template (a .drwdot) or the default drawing template. Then place views with create_drawing_view; for a whole drawing from a model in one call, use generate_drawing_package instead (both in the drawing toolset). Needs: SolidWorks running. Changes: opens a new drawing document. Returns: drawing with name and template.

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 drawing. `name` is required but only a label: the reply gives SolidWorks' own name (Draw1, ...); `template` has a default.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation profile is covered. The description adds context annotations cannot carry: the SolidWorks-running prerequisite, the side effect of opening a new document and making it active, and the naming quirk (the supplied name is a label; SolidWorks names it Draw1). The only weakness is repeating return fields that the output schema already documents.

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 core action, then compactly organized into Needs/Changes/Returns, with sibling routing mentioned before the boilerplate. Minor waste only in the Returns clause, which restates fields the output schema already contains.

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 agent has everything needed: prerequisite (SolidWorks running), state change (new active document), alternative paths for the drafting workflow, and the parameter meaning. Annotations and output schema cover safety and return shape, so nothing material is missing.

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%, and the schema itself already explains that `name` is a label and `template` defaults to null. The description reinforces the template semantics ("a .drwdot" or "the default drawing template") but adds no format, path, or validation detail beyond the structured fields, so baseline 3 applies.

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 with a scope qualifier: "Create a new, empty drawing document and make it active." The word "empty" and the follow-up about placing views make clear this is not the model-driven drawing generator, distinguishing it from create_drawing_view and generate_drawing_package by name.

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 routing is provided: use this to create the shell, then "place views with `create_drawing_view`"; or "for a whole drawing from a model in one call, use `generate_drawing_package` instead." It names both alternatives and the condition selecting each, leaving nothing to inference.

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