Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_dimension

Changes a named sketch or feature dimension by value and rebuilds the SOLIDWORKS model, restoring the old value if the rebuild fails.

Instructions

Change a dimension by name and rebuild the model. Works on sketch dimensions and feature dimensions (depths, pattern spacing, fillet radius, ...). If the new value breaks a feature on rebuild, the old value is restored and the call fails. A size the tools dimensioned from the drawing (DrawnN) becomes the user's when set: it is renamed (the result says to what). A dimension an equation drives is refused, naming the equation (change it with set_equation). With more than one configuration, configurations is required: without it the call is refused, listing them.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "set_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDimension name from list_dimensions, e.g. 'D1@Sketch1'
unitNomm, cm, m, inch or ft
valueYesNew value (length in unit, degrees for an angle, or a whole number for a pattern count)
configurationsNoConfiguration names to change, or ["all"]. Needed when the model has more than one configuration; with one, leave it out.

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?

No annotations are provided, so the description carries the full behavioral burden and does it well: it discloses atomic rollback ("the old value is restored and the call fails"), a side effect beyond the mutation itself (DrawnN dimensions get renamed and the result reports the new name), and the refusal conditions with their remedies. These are exactly the behaviors an agent cannot infer from the schema.

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?

Four tight sentences, front-loaded with the action and scope, then hollowed out to consequences and edge cases. No sentence repeats the name or restates the schema; each adds a distinct behavioral fact.

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 mutation tool with no annotations and no output schema, this is complete: rollback behavior, refusal conditions, preconditions to supply configurations, and the shape of the relevant return information (the new dimension name) are all covered.

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, and the description adds real meaning on top: it explains the consequence of omitting configurations (refused, with configurations listed), the rename side effect on name, and value units for angles and pattern counts. The one gap is that unit is never discussed in the description, though the schema documents it.

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 ("Change a dimension by name and rebuild the model") and immediately bounds scope to sketch and feature dimensions with concrete examples (depths, pattern spacing, fillet radius). It also makes clear this is not the equation path, naming set_equation as the sibling to use instead.

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 when-to-use context (sketch and feature dimensions) and two hard exclusions: equation-driven dimensions are refused, and multi-configuration models require the configurations argument. In both cases it names the alternative or the remedy, so the agent can route correctly.

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