Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Technical Drawing

create_technical_drawing

Adds a model's front, top, and side views to the active drawing sheet in one call, starting a technical drawing with third- or first-angle projection.

Instructions

Place a model's three standard views (front, top and side) on the active drawing sheet in one call.

Use it to start a drawing's views quickly; for one view, use create_drawing_view, and to create and save a complete drawing from a model file, use generate_drawing_package. Views are laid out in projection (third-angle by default). Needs: an open, active drawing and the model file on disk. Changes: adds three views to the sheet. Returns: data with views (the names added), model_path, projection and the view counts.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe model to draw. Give `model_file`; `projection` is third_angle unless you pass first_angle.

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 and destructiveHint=false, so the write-but-non-destructive profile is covered. The description adds genuinely new behavioral context: prerequisites (an open, active drawing and the model file on disk) and the concrete effect ('adds three views to the sheet'). It stops short of warning that repeat calls would stack extra views (relevant given idempotentHint=false), so it is strong but not exhaustive.

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 routed to alternatives, then structured with explicit Needs/Changes/Returns labels. The Returns sentence partially duplicates the existing output schema's fields, which is the only mildly wasteful element in an otherwise tight definition.

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?

For a one-parameter mutation tool with an output schema, this covers everything an agent needs to invoke it correctly: prerequisites, the side effect, the alternatives, and the projection convention. Return values are also sketched, so nothing material is missing even for an agent that does not inspect the output schema.

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 every parameter is already documented, including the third_angle default. The description restates that a model file is needed and that projection defaults to third-angle, adding no format or syntax detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

Description opens with a specific verb and resource: place a model's three standard views (front, top, side) on the active drawing sheet in one call. The 'in one call' framing and the three-mentioned views make it immediately distinguishable from create_drawing_view (single view) and generate_drawing_package (complete saved drawing).

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 when-to-use ('start a drawing's views quickly') plus two named alternatives with the exact condition that selects each: create_drawing_view for one view, generate_drawing_package for a complete saved drawing from a model file. Nothing is left 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