Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Sketch Dimension

add_sketch_dimension

Adds a driving dimension to sketch entities—linear, angular, radial, or diameter—to fix sizes, fully define the sketch, and allow later edits.

Instructions

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

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. 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. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value."New value: +"The dimension. `entity1` and `value` (mm, or degrees for\nangular) are required; `entity2` and `dimension_type` (linear) have\ndefaults."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds that no dialog opens, that the operation resizes geometry to the given value, and that it returns a dimension object with id/type/value/entities. That is meaningful effect disclosure beyond annotations, though it doesn't mention failure modes (e.g., over-defined sketches) or whether the change is undoable.

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-loads the purpose in one clause, then uses compact labeled segments (Needs / Changes / Returns) with no filler. Every sentence carries actionable information.

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?

Given a single nested input object, existing annotations, and an output schema, the description still covers prerequisites, geometry side effects, entity sourcing, and type-specific entity requirements. An agent has everything needed to invoke it correctly.

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; the description earns more by tying entity1/entity2 to IDs returned by the add_* tools and spelling out that angular needs two connected lines while radial/diameter need a circle or arc. It adds cross-tool meaning the schema does not.

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 (add) and resource (driving dimension) plus the supported dimension types (linear, angular, radial, diameter). An agent can tell this apart from set_dimension, which the description explicitly assigns to later modification.

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 the when (fix a size so the sketch is fully defined), the prerequisite (an open sketch from create_sketch), the alternative for modification (set_dimension), and the entity pairing rules per dimension type. That is explicit routing and prerequisite coverage rather than inference.

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