Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Drawing View

create_drawing_view

Adds a single named part or assembly view to the active drawing sheet, enabling individual placement of orthographic, isometric, section, or detail views.

Instructions

Place one named view of a part or assembly on the active drawing sheet.

Use it to add views one at a time; for the three standard views in one call, use create_technical_drawing, and for a whole drawing from a model, use generate_drawing_package. Needs: an open, active drawing and the model file on disk. Changes: adds a view to the sheet. Returns: data with the view's name, orientation, position, scale and the view counts before and after.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe view. `model_path` and `view_type` (front, back, left, right, top, bottom, isometric (iso), trimetric, dimetric or current) are required; `position_x`/`position_y` (mm on the sheet) and `scale` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses prerequisites and the mutation ('adds a view to the sheet') and outlines the returned `data` fields and before/after view counts. It does not address failure behavior, what happens if a view is placed at an occupied position, or why the operation is non-idempotent (duplicate views on repeat calls), which would have completed the picture for a write tool.

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 with the core action, then explicitly labeled 'Use it to', 'Needs', 'Changes', and 'Returns' segments. Every sentence carries distinct information and there is no filler.

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 nested-parameter write tool with an output schema and annotations already declaring non-readonly, non-destructive behavior, the description covers purpose, prerequisites, side effect, and alternatives. Nothing an agent needs in order to select and invoke it correctly 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 coverage is 100%, so the schema already documents every nested property and default; the description only restates required fields and defaults. Its enumeration of `view_type` values (front, back, left, right, top, bottom, isometric, trimetric, dimetric, current) actually diverges from the schema's own parenthetical (orthographic, isometric, section, detail), which adds ambiguity rather than clarity.

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 opens with a specific verb and resource: 'Place one named view of a part or assembly on the active drawing sheet.' It immediately scopes the tool to a single view, which cleanly separates it from `create_technical_drawing` (three standard views) and `generate_drawing_package` (whole 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?

It gives explicit routing conditions: use this one for views 'one at a time', `create_technical_drawing` for the three standard views in one call, and `generate_drawing_package` for a whole drawing from a model. It also states prerequisites (an open active drawing, model file on disk), which is the when-to-use condition most easily missed.

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