Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_sketch_dimension

Adds a driving dimension to the open sketch and optionally sets its value, measuring length, diameter, radius, distance, or angle from selected entities. Rejects conflicting dimensions.

Instructions

Add a driving dimension in the open sketch and optionally set its value. What gets measured follows from the entities: one line = length, circle = diameter, arc = radius, two points / a point and a line / two parallel lines = distance, two non-parallel lines = angle (degrees). The value must be greater than 0. A dimension that over-defines the sketch replaces a size the tools added from the drawing (named DrawnN; the result says which); one that conflicts with the user's own dimensions or relations, or that the sketch cannot satisfy, is rejected and not left in it, naming the conflicting dimensions. Several dimensions in one call: the others in more; if any is rejected, none of the call's stays. Returns the sketch's definition status. A value on a model with more than one configuration needs configurations: 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": {
      "entities": "<entities>"
    },
    "name": "add_sketch_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
moreNoFurther dimensions in this call, e.g. [{'entities': ['origin', '2:start'], 'value': 20, 'orientation': 'horizontal'}]; same unit
unitNomm, cm, m, inch or ft
valueNoValue to set (length in unit, or degrees for an angle). Omit to keep the size as drawn.
entitiesYesEntity references as strings, e.g. ['1'], ['origin', '1:start'], ['2', '3'], or a model edge by a point on it: ['1:center', 'edge:80,40,5']
orientationNoFor distances between points: measure horizontally, vertically, or aligned (auto)auto
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.6/5.0
Behavior5/5

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

No annotations are supplied, and the description carries the full burden well: it discloses that an over-defining dimension silently replaces a tool-created DrawnN size, that conflicting dimensions are rejected and named, that the batch is atomic ('if any is rejected, none of the call's stays'), and that a missing configurations argument causes a refusal listing the available configurations. These are exactly the side effects an agent needs before invoking a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause and every subsequent sentence adds a distinct constraint rather than repeating the schema. It is dense and some clauses are compressed into run-ons (notably the batching/atomicity sentence), which costs a little readability but not correctness.

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 six-parameter mutation with no annotations and no output schema, the description covers the gaps that matter: entity semantics, value constraints, configuration preconditions, failure modes, atomicity, and the fact that it returns the sketch's definition status. Nothing an agent needs to call it correctly is left unstated.

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 would be 3, but the description adds real meaning beyond the schema: it explains that the measured quantity is derived from the entity types supplied (single line = length, circle = diameter, arc = radius, point pairs or parallel lines = distance, non-parallel lines = angle in degrees). That derivation is not inferable from the entity array alone and directly shapes how the agent must build the arguments.

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?

Opens with a specific verb and resource: 'Add a driving dimension in the open sketch and optionally set its value.' The phrase 'in the open sketch' implicitly separates it from add_drawing_dimension, and it immediately qualifies scope with the entity-to-measurement mapping, so an agent knows exactly what the tool creates.

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?

Gives clear use conditions: value must be greater than 0, configurations required on multi-configuration models, and what happens with over-defining or conflicting dimensions. It never explicitly routes to a named alternative such as add_sketch_relation or set_dimension, so the agent must infer the boundary from behavior rather than a stated rule.

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