Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

get_cut_list

Reads the cut list of the active weldment part, returning each member's name, quantity, tip-to-tip length, profile, material and end angles in your chosen unit.

Instructions

Read the cut list of the active weldment part: for each item its name, quantity, length (measured along each member, tip to tip), description (profile), material and end angles.. After butt corners (structural_member butt1 / butt2: SolidWorks' pinwheel) every member is exactly as long as its path, with square ends. 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": "get_cut_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for the lengths (mm, cm, m, inch or ft)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 does declare 'Read-only' and explains the non-obvious semantics that lengths are measured tip-to-tip along each member path and are exact square-ended after butt corners. It does not disclose what happens when no active weldment is open or what a failure looks like, which keeps it 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?

The core purpose and returned fields are front-loaded in one dense sentence, with the butt-corner caveat following. The geometry sentence is long and slightly garbled (double period, 'butt corners (structural_member butt1 / butt2: SolidWorks' pinwheel)'), which costs a bit of readability.

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?

With no output schema and no annotations, the description must supply both return fields and behavior, and it largely does: it lists every returned field and defines how length is measured. Remaining gaps are the empty/error case (no active weldment) and the default unit, which an agent would need before calling.

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% and the single 'unit' parameter is already documented with allowed values in the schema. The description mentions lengths but never ties them to the unit parameter or states a default, so it adds nothing 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 ('Read the cut list of the active weldment part') and then enumerates exactly what each item returns: name, quantity, length, description/profile, material, end angles. That level of specificity makes it clearly distinct from generic siblings like get_sheet_metal_info or list_features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'active weldment part' implies the required document context, but there is no explicit when/when-not guidance and no named alternative for reading geometry of non-weldment documents. The structural_member butt1/butt2 reference explains a measurement convention rather than routing the agent to another tool.

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