Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

arrange_dimensions

Spread dimensions in drawing views to prevent overlap; returns text positions and any remaining pairs closer than 2 mm. Use after adding dimensions or creating a drawing with dimensions.

Instructions

Spread the dimensions of a drawing view (or of every view) so they stop overlapping; use it after create_drawing(dimensions=true) or after adding dimensions. Returns where each dimension text ended up and any pairs still closer than 2 mm.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arrange_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of the length inputs: mm (the default, whatever set_units says), cm, m, inch or ft. Results are in mm
viewNoName of one view (default: every view)
spacingNoDistance between stacked dimension lines (in unit; default 6 mm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the operation repositions dimension text and that the response reports final text locations plus any pairs still closer than 2 mm, but it does not say whether existing manual placements are destroyed, whether it can fail or no-op, or whether it is safe to run repeatedly.

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?

A single tight sentence pair: the action and scope come first, the usage trigger second, and the return information last. No filler or repetition.

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 a lightweight, no-required-parameter layout tool with no output schema, the description covers purpose, trigger, and return contents, which is most of what an agent needs. The only missing piece is the mutation risk to manually placed dimensions, which matters because there are no annotations to signal it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with only 3 optional parameters, so the schema already documents unit, view and spacing including defaults. The description only echoes the 2 mm overlap threshold and adds no syntax, interaction, or default behavior beyond the schema, so the baseline 3 applies.

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?

"Spread the dimensions of a drawing view (or of every view) so they stop overlapping" gives a specific verb (spread/rearrange), a specific resource (dimension annotations in a drawing view), and the scope choice between one view and all views. It is clearly distinct from siblings like add_drawing_dimension and list_dimensions.

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?

It explicitly states when to reach for it: after create_drawing(dimensions=true) or after adding dimensions, which tells the agent this is a cleanup pass rather than a creation step. It does not name an alternative or say when not to use it (e.g., that running it after manual placement will overwrite that placement), leaving a small gap.

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