Lists dimensions for a SolidWorks document or selected feature, including full names and values in millimeters or degrees so you can identify parameters for edits.
Driving dimensions with full names ('D1@Boss-Extrude1', 'span_d@Sketch1') and values in mm / degrees.
| Name | Required | Description | Default |
|---|---|---|---|
| doc | No | Document title or path. Defaults to the active document. | |
| feature | No | Only this feature's dimensions. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds critical behavioral context by specifying that names include file-like paths (e.g., 'D1@Boss-Extrude1') and defines the expected units (mm/degrees). This is valuable information not present in the schema or annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is extremely efficient, using a single sentence to deliver its entire functional contract, purpose, and data format expectations without any fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema, the description performs a vital role by explicitly defining the content of the returned data (full names, values, and units), which is essential for an AI agent to successfully parse and utilize the tool's results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Since the schema coverage is 100%, the baseline for this dimension is high. The description confirms that parameters like 'doc' and 'feature' are used to narrow the scope of the dimension search, but it does not add novel semantic information beyond what the schema outlines.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the purpose is to retrieve 'Driving dimensions'. It specifies the content of the result (names and values) and provides exact format examples, making its function unambiguous within the CAD context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the tool's scope (listing dimensions) is clear, the description does not provide guidance on when to use it versus alternative listing or measurement tools (e.g., `sw_get_properties` or `sw_list_features`). The usage is implied by the nature of the data returned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.