Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_dimensions

Lists a SOLIDWORKS model’s dimensions by feature and returns the names required to set values or update equations, helping you find dimensions before changing them.

Instructions

List the model's dimensions by feature, with the names set_dimension uses (D1@Sketch1 for a sketch dimension, D1@Boss-Extrude1 for an extrude depth, for example). A dimension an equation drives shows that equation: change it with set_equation.

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_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
featureNoOnly this feature or sketch (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully reveals two behavioral traits beyond the schema: results are keyed by the same names set_dimension consumes, and equation-driven dimensions report the driving equation, signaling they are indirectly edited. It omits prerequisites (active document requirement), whether units affect only labeling, and any behavior for missing/empty models.

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?

Two tightly packed sentences with no filler; the purpose and return naming convention come first, followed by the cross-tool routing note. Every clause earns its place.

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

Completeness3/5

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

With no output schema and no annotations, the description must cover return shape, and it partially does by explaining the name format and equation indicator. It still leaves the list's structure, ordering, and document preconditions unstated, which matters for a tool returning a variable-length collection.

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 both parameters (unit, feature) are already documented, establishing a baseline of 3. The phrase "by feature" loosely corroborates the feature filter, but the description adds no syntax or semantics for unit (e.g., whether it converts values or just formats them) beyond the schema.

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 ("List the model's dimensions") with scope ("by feature") and defines the returned naming convention with concrete examples (D1@Sketch1, D1@Boss-Extrude1). It also distinguishes itself from set_dimension by adopting its name format and from set_equation by routing equation-driven dimensions there.

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?

Gives an explicit alternative for one case: if a dimension is equation-driven, change it with set_equation rather than this tool. It does not spell out broader usage context such as needing an open/active document or when to prefer list_features first, but the primary read-vs-write split is clear.

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