Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Insert Model Dimensions

insert_model_dimensions

Imports the model’s marked-for-drawing dimensions into the active drawing’s orthographic views, keeping each dimension once and removing repeats; run arrange_dimensions afterward to place them.

Instructions

Bring the model's dimensions into the active drawing's views, each dimension shown once.

Imports the model's "marked for drawing" dimensions view by view; a repeat in a later view is deleted. Pictorial views (isometric, dimetric, trimetric) are skipped unless named. Falls back to SolidWorks AutoDimension only when nothing could be imported. SolidWorks places them inside the views, so run arrange_dimensions next. Needs: an open, active drawing with views. Changes: adds dimensions to the views. Returns: data with per-view views (before/after counts, duplicates_removed), dimensions_added, unique_dimensions, skipped_pictorial_views and the method used. An unknown view is not_found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insert_model_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoWhich views. Nothing is required: give `view_name` for one view, or omit it for every view; `include_hole_wizard` has a default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation; the description goes further by disclosing what is destroyed (duplicates in later views), what is skipped (isometric/dimetric/trimetric), what is mutated (dimensions added to views), and the fallback path. This is exactly the behavioral context the annotations cannot convey.

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?

Dense but front-loaded, with scoping in the first sentence and clearly labeled 'Needs:', 'Changes:', 'Returns:' clauses. Every sentence conveys an operational fact with 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?

Covers prerequisites, mutation effects, deduplication behavior, fallback, follow-up tool, and error case, and summarizes the return payload despite an output schema existing. Nothing an agent needs to call this 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%, and the description largely restates the schema's view scoping ('unless named', one view vs. all). Its only added value is the error semantics for an unknown view (`not_found`), which is marginal against an already complete schema.

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: bring the model's 'marked for drawing' dimensions into the active drawing's views, one per view. It is clearly distinguished from `arrange_dimensions` (which should run afterwards) and from inspection tools like `list_model_dimensions`.

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?

Gives explicit preconditions ('an open, active drawing with views'), a documented fallback (AutoDimension only when nothing could be imported), a scoping rule (pictorial views skipped unless named), and a direct follow-up instruction to run `arrange_dimensions` next.

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