Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Set Dimension

set_dimension
Idempotent

Change one length dimension of an active part or assembly in millimeters and rebuild to resize it, applying the update to the active or selected configurations.

Instructions

Change one length dimension of the active model, in mm, and rebuild.

Use it to resize an existing model; find the full name with list_model_dimensions and check the result with rebuild_model or verify_model. The value is always millimetres. It changes the active configuration only, unless configurations is "all" or a list of names. Needs: an open part or assembly. Changes: the dimension and the geometry it drives. Returns: dimension_update with name, old_value, new_value and configurations (the names it was set in).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe change. `value` (mm) is required, with `name` (or `dimension_name`) such as "D1@Sketch1"; `units` is not used.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, and the description goes further by disclosing scope of mutation ("changes the dimension and the geometry it drives"), configuration scoping rules, and the rebuild side effect. The only slack is that the "Returns:" sentence largely restates what an existing output schema presumably covers.

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?

Verb-and-scope first, then labeled "Needs:", "Changes:", and "Returns:" clauses that make scanning trivial. Only minor redundancy (millimetres stated twice, return shape duplicated with the output schema), with no wasted exposition.

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-parameter mutation with a nested input object and an output schema, the description covers prerequisites, mutation scope, configuration targeting, rebuild intent, and follow-up verification. An agent has everything needed to invoke it correctly without opening the schema.

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 baseline is 3, but the description adds real meaning: the `value` is strictly millimetres, `configurations` defaults to affecting the active configuration only unless set to "all" or a name list, and the name must be a fully qualified dimension identifier. The `units` alias being unused is also clarified in 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, resource, and scope: "Change one length dimension of the active model, in mm, and rebuild." This distinguishes it cleanly from creating dimensions (add_dimension) or reading them (get_dimension), and the units plus single-dimension constraint are stated up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the use case ("resize an existing model"), names the discovery sibling (`list_model_dimensions`) for the dimension name, and the verification siblings (`rebuild_model`, `verify_model`). It also states the prerequisite of an open part or assembly. It stops short of an explicit exclusion (e.g., when to prefer `set_equation` for formula-driven values or `add_dimension` for new dimensions).

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