Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Drawing View

add_drawing_view

Place one named part or assembly view on the active drawing sheet; requires an open drawing and the model file on disk. Only operation "add" is supported; prefer create_drawing_view.

Instructions

Deprecated: use create_drawing_view.

Place one named view of a part or assembly on the active drawing sheet; the same as create_drawing_view.

Prefer create_drawing_view; this tool reaches the same code and is kept for existing callers. It only adds views: an operation other than "add" is refused. 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.

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": "add_drawing_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe view. Give `model_file` and `view_type` (front, back, left, right, top, bottom, isometric (iso), trimetric, dimetric or current); `position` ([x, 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.8/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description goes well beyond them by declaring the side effect ('adds a view to the sheet'), the accepted-operation constraint, the required state (active drawing, model on disk), and the returned fields. Nothing about the mutation's blast radius is left to inference.

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 deprecation routing is correctly front-loaded and the remaining sentences are short, labeled clauses (Needs / Changes / Returns). There is minor redundancy between 'the same as `create_drawing_view`' and 'reaches the same code', and the Returns section partly duplicates the output schema.

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 single nested-parameter mutation with an output schema, the definition covers everything an agent needs: predecessor to prefer, prerequisites, the one behavioral constraint, the side effect, and the return payload. No gap remains that would cause a misinvocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning the schema lacks: it enumerates the valid `view_type` values (front, back, left, right, top, bottom, isometric/iso, trimetric, dimetric, current) where the schema only says 'Type of view', and it states that `position` is [x, y] in millimetres. It does not clarify `parent_view`, `parameters`, or `drawing_path`, keeping it short of a 5.

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 ('Place one named view of a part or assembly on the active drawing sheet') and immediately identifies it as identical to the sibling `create_drawing_view`. The deprecation notice is front-loaded, so an agent knows both what the tool does and that it is the legacy path.

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 explicitly names the preferred alternative twice and gives the reason ('reaches the same code and is kept for existing callers'), plus a hard when-not: an `operation` other than "add" is refused. Prerequisites (open active drawing, model file on disk) are stated, so the agent knows the preconditions to satisfy before calling.

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