Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Model Dimensions

list_model_dimensions
Read-onlyIdempotent

Lists every dimension in an open part or assembly with full name and value, optionally filtered by feature, so you can find the exact name needed to get or change it.

Instructions

List every dimension in the active part or assembly with its full name and value.

Use it to find a dimension in an existing model before changing it: each full_name (e.g. "D1@Sketch1") is the name get_dimension and set_dimension take. Each dimension is listed once, under the feature its full name names after the @ (D1@Plane1 under Plane1, never also under a cut sketched on that plane). Needs: an open part or assembly. Read-only. Returns: data, one entry per dimension with full_name, feature, value (document units), system_value (metres or radians) and read_only.

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": "list_model_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: give `feature_name` to list the dimensions that feature owns, or omit it for every dimension.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds the prerequisite 'Needs: an open part or assembly' and a non-obvious deduplication rule (a dimension appears once, under the feature named after the '@', never also under a downstream cut). It does not cover behavior when no document is open or the ordering of results, so it stops short of a 5.

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-loaded statement followed by clearly labeled 'Needs:', 'Read-only.' and 'Returns:' segments; each sentence carries information. The deduplication example is somewhat verbose with its parenthetical illustration, which keeps it just under top marks.

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 read-only lister with an output schema, the description supplies prerequisites, result shape and cross-tool routing, which is sufficient to call it correctly. The one meaningful omission is any mention of the feature_name filter, a real gap since it is the tool's only parameter.

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%, so feature_name is already fully documented in the schema. The description never mentions the optional feature filter at all and instead says 'every dimension in the model', adding no meaning beyond the schema and slightly under-representing the tool's scoping ability. 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?

Opens with a specific verb and resource plus scope ('List every dimension in the active part or assembly with its full name and value'), and immediately distinguishes itself from get_dimension and set_dimension by explaining that its full_name output is what those tools consume.

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?

States an explicit use case ('find a dimension in an existing model before changing it') and names the downstream alternatives (get_dimension, set_dimension), so the agent knows both when to call this and what to do with the result.

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