Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Drawing Dimension

add_dimension

Adds a reference dimension to an active SolidWorks drawing view using sheet-coordinate points on edges or vertices; measures distance, length, angle, radius, or diameter.

Instructions

Add one dimension to a drawing view, between edges picked by points on the sheet.

Give points in sheet mm on a view's edges or vertices (read view outlines with check_drawing). Two parallel edges give their distance; one edge its length; a circle's edge its radius or diameter; two lines their angle. For the model's own dimensions use insert_model_dimensions instead. Needs: an open, active drawing. Changes: adds a reference dimension. Returns: dimension with name, value and units (mm, deg for angular).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe dimension. `dimension_type`, `entity1_point` and `position` are required; `entity2_point` for two entities.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description goes further by naming the mutation ('adds a reference dimension'), the state prerequisite (open active drawing) and the return payload shape. That is meaningful behavior beyond the structured hints and is consistent with them.

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 broken into scannable Needs/Changes/Returns segments with no filler. Dense but every sentence carries information an agent needs to call it correctly.

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-object mutation tool it covers prerequisite state, the effect of the call, the output fields and units, and the sibling alternative. With an output schema present and full schema coverage, nothing essential is left for the agent to guess.

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, but the description adds geometric meaning the schema does not: two parallel edges measure distance, one edge its length, a circle's edge radius or diameter, two lines their angle. It does not explicitly restate the per-type entity2_point requirement, leaving that mapping partly to inference from the 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 ('Add one dimension to a drawing view') plus the mechanism ('between edges picked by points on the sheet'), and explicitly separates itself from insert_model_dimensions. An agent can distinguish it from check_drawing, insert_model_dimensions and the generic add_* siblings without opening a schema.

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 an explicit alternative and the condition that selects it ('For the model's own dimensions use insert_model_dimensions instead'), plus a prerequisite ('Needs: an open, active drawing') and a pointer to check_drawing for reading view outlines. When-to-use, when-not-to-use, and setup are all covered.

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