Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Arrange Drawing Dimensions

arrange_dimensions
Idempotent

Moves drawing dimensions into tidy rows outside their views and checks the sheet for overlaps, keeping each dimension readable and reporting any that cannot be placed.

Instructions

Move drawing dimensions out of their views into tidy rows so nothing overlaps, then check the sheet.

Rows start 8 mm outside each view, 7 mm apart, shortest span nearest the view. A dimension with no room stays put and is listed in unplaced. The check reads back every text box and line: no text on text, no line through text or across a view, nothing off the sheet. Use it after insert_model_dimensions. Needs: an open, active drawing. Changes: moves dimensions on the sheet. Returns: data with dimensions, moved, overlaps_before, overlaps_after and unplaced. If any overlap remains the call is an error whose data lists remaining_overlaps; try a smaller sheet scale (set_sheet_scale).

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
input_dataNoWhich views. Nothing is required: give `view_name` for one view's dimensions, or omit it for every view.

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 declare readOnly=false, destructive=false and idempotent=true; the description adds genuinely new behavior: the exact placement geometry (8 mm outside each view, 7 mm apart, shortest span nearest), the fallback for dimensions with no room (`unplaced`), and the error contract where remaining overlaps surface as `remaining_overlaps` in `data`. What is not disclosed is whether the move is reversible/undoable on an already-arranged sheet, so the agent cannot fully confirm the destructive=false claim for repeat runs. That is a real but narrow gap against otherwise rich disclosure.

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?

The first sentence front-loads purpose and the second delivers the placement rules; the compressed 'Needs:/Changes:/Returns:' block then packs prerequisites, side effects and return keys into one line each. Every sentence carries distinct information with no restatement of the schema or title.

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 mutating one-parameter tool with an output schema, the description covers purpose, prerequisites, side effects, return keys, and the failure path with a suggested recovery. Even though the output schema exists, naming `dimensions`, `moved`, `overlaps_before/after` and `unplaced` tells the agent how to interpret the result.

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% and the single `view_name` parameter is already documented in detail, including the default of every view and the note that the overlap check always covers the whole sheet. The description adds no syntax, format, or example beyond that, so it sits at the baseline where the schema does the work.

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?

The description opens with a specific verb and resource ('Move drawing dimensions out of their views into tidy rows') plus the secondary effect ('then check the sheet'), which tells an agent exactly what the call accomplishes. It is clearly distinguished from the setup tool (`insert_model_dimensions`) and the remediation tool (`set_sheet_scale`), so no schema reading is needed to identify it.

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?

It states sequencing explicitly ('Use it after `insert_model_dimensions`'), gives the prerequisite ('Needs: an open, active drawing'), and routes the agent to an alternative when the call fails ('try a smaller sheet scale (`set_sheet_scale`)'). Usage is bounded to one view or all views with no ambiguity about what to do next.

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