Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Dimension

add_sketch_dimension

Adds driving dimensions to sketch entities—linear, angular, radial, diameter, or ellipse axis—to fix sizes, fully define the sketch, and enable later edits via set_dimension.

Instructions

Add a driving dimension to sketch entities: linear, angular, radial, diameter or an ellipse axis.

Use it to fix a size so the sketch is fully defined and can be changed later with set_dimension. Entities are the ids the add_* tools returned; two connected lines for angular, a circle or arc for radial or diameter, an ellipse for major_axis or minor_axis (value is the whole axis; the dimension runs from the centre, so it shows half). No dialog opens. Needs: an open sketch (create_sketch). Changes: adds the dimension and resizes the geometry to value. Returns: dimension with id, type, value and the entities.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe dimension. `entity1` and `value` (mm, or degrees for angular) are required; `entity2` and `dimension_type` (linear) have defaults.

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?

Goes well beyond the annotations by disclosing the real side effect ('resizes the geometry to value'), that no dialog opens, and the exact return shape. The prerequisite of an open sketch is also surfaced, which annotations could never 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?

Front-loaded verb-and-resource sentence, then labeled 'Needs / Changes / Returns' clauses that make each fact scannable. No filler or repetition of schema text.

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 with an output schema, the description covers prerequisites, side effects, entity-to-type mapping, and return contents. Nothing an agent needs to call it correctly is missing.

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 already 100%, yet the description adds genuine meaning: which entity combinations map to which dimension type (two connected lines for angular, circle/arc for radial or diameter, ellipse for major_axis/minor_axis) and that the ellipse value is the whole axis while the dimension displays half. Only entity2's dual-entity semantics are left mostly to 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 a driving dimension to sketch entities') and enumerates the supported dimension kinds: linear, angular, radial, diameter, ellipse axis. An agent can distinguish it from set_dimension purely from this sentence.

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 use case ('fix a size so the sketch is fully defined'), names the follow-up alternative set_dimension for changing the value later, and states the prerequisite tool create_sketch. When-to-use and the cooperating siblings are both 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