Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Auto-Dimension Drawing View

auto_dimension_view

Adds baseline or chain reference dimensions to one SolidWorks drawing view from its edges; use when no model dimensions exist, then arrange any overlaps.

Instructions

Dimension one drawing view with SolidWorks' auto-dimension (baseline or chain).

It adds reference dimensions measured from the view's edges; prefer insert_model_dimensions, which shows the model's own (driving) dimensions, and use this for a view that has none to bring in. Dimensions may overlap: run arrange_dimensions after. It fails when nothing is added. Needs: an open, active drawing with that view. Changes: adds dimensions. Returns: data with added and the counts before and after.

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": {
      "input_data": "<input_data>"
    },
    "name": "auto_dimension_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe view. `view` is required; `scheme` is baseline.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the mutation/safety profile; the description adds the prerequisites (an open, active drawing containing that view), the effect ('adds dimensions'), and the failure mode. It stops short of saying what happens on a repeat call — annotations mark it non-idempotent, but the description never warns that re-running may stack additional reference dimensions.

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?

Front-loads the purpose, then uses compact 'Needs / Changes / Returns' labels, which read well. The returns sentence is largely redundant against the output schema, and the parenthetical 'baseline or chain' duplicates an enum already in the schema.

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 one-parameter mutation tool, everything needed to call it correctly is present: prerequisites, sibling alternative, follow-up tool, failure mode, and effect. The existence of an output schema covers return details, so this is complete.

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 coverage is 100%, with `view` sourced from `list_drawing_views` and `scheme` enumerated with a baseline default, so the schema carries the load. The description only restates 'baseline or chain' without adding selection guidance for choosing between them, so it lands at the baseline 3.

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 ('Dimension one drawing view') plus the mechanism ('auto-dimension (baseline or chain)'), and explicitly distinguishes itself from `insert_model_dimensions`. An agent can identify the tool and its counterpart without opening either schema.

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 routing: prefer `insert_model_dimensions` for the model's driving dimensions, use this only for a view with none to bring in, and run `arrange_dimensions` afterward because dimensions may overlap. It also names the failure condition ('fails when nothing is added'), which is the kind of when-not guidance most definitions omit.

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