Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_drawing_dimension

Add driven reference dimensions to a drawing view between edges or points, measuring distance or angle, or line length, circle diameter, and arc radius without altering the model.

Instructions

Add a dimension to a drawing view between two of its edges or points, chosen by the ids that list_drawing_views(view=...) reports (E3 = an edge, P2 = a point). Two parallel lines, two points, a point and a line, or a circle and a line or circle (measured from the centre) give a distance; two crossing lines give an angle. With only first: the length of a line, the diameter of a circle or the radius of an arc. direction forces a horizontal or vertical measurement. The dimension is a reference (driven) one: it shows the model's size and cannot change it. The same dimension again on the same entities is refused; one equal in size to a dimension already in the view is added with a warning naming it. Returns its name, value and place. Several dimensions in one view: give the others in more (one call); if any is refused, none of the call's dimensions stays.

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": {
      "view": "<view>",
      "first": "<first>"
    },
    "name": "add_drawing_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
moreNoFurther dimensions in the same view in this call, e.g. [{"first": "E2", "second": "E5"}]; placed beside the first
unitNoUnit of the length inputs: mm (the default, whatever set_units says), cm, m, inch or ft. Results are in mm
viewYesName of the view
firstYesEdge or point id, e.g. E1 or P1
secondNoSecond edge or point id (optional)
x_sheetNoWhere the dimension text goes, from the left edge (in unit, mm by default) of the sheet
y_sheetNoWhere the dimension text goes, from the bottom edge (in unit, mm by default) of the sheet
directionNoForce the measuring direction (default: SolidWorks decides)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it declares the dimension is reference (driven) and cannot change the model, that exact duplicates are refused, that equal-size dimensions are added with a warning naming the conflicting one, and that a multi-dimension call is all-or-nothing. Return content ('name, value and place') is also disclosed.

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?

One dense paragraph that is front-loaded with the core action and follow-on constraints in priority order; no filler. The batching sentence ('give the others in more (one call)') is slightly awkward but still parses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutating tool with no annotations and no output schema, the description covers geometry semantics, failure modes, atomicity and return values. Minor gaps remain: it does not say how a view name is obtained beyond the list_drawing_views reference or how sheet placement coordinates interact with `unit`.

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; the description still adds meaning by defining the E#/P# id convention, the optionality and effect of `second`, how `direction` forces horizontal/vertical measurement, and how `more` batches further dimensions placed beside the first.

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 dimension to a drawing view between two of its edges or points') and immediately scopes it to entity ids reported by list_drawing_views, which separates it from a sketch-dimension or generic set_dimension tool.

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?

Enumerates the valid entity pairings and what each yields (distance for parallel lines/points/circle-line, angle for crossing lines) and what happens with only `first`. It does not explicitly contrast with siblings like add_sketch_dimension or set_dimension, so there is no exclusion guidance, but the when-to-use surface is well 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