Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Extruded Cut

create_cut_extrude

Cuts holes, slots, or windows from an active solid body using a closed sketch profile after exiting the sketch, supporting blind, through-all, and both-direction cuts.

Instructions

Cut material from the active part with a closed sketch profile: holes, slots, windows.

Use it after exit_sketch. Pass sketch_name unless the sketch you just closed is the one: with no name only that sketch is used, and any doubt is an error naming the sketches found. A one-way cut that finds no material is retried the other way (direction_flipped). For a sketch inside the body, use ThroughAllBoth. Needs: an open part with a solid body. Changes: adds a Cut-Extrude feature. Returns: cut_extrude (name, sketch_name, direction_flipped) and measured_change (volume, bounding box and solid-body count before and after; left out when the model can't be read).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe cut. `depth` (mm) is required; `sketch_name`, `end_condition` (Blind, ThroughAll, ThroughAllBoth), `both_directions`, `reverse_direction` and `draft_angle` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"Depth, direction, draft, and\noptional sketch_name parameters."New value: +"The cut. `depth` (mm) is required; `sketch_name`,\n`end_condition` (Blind, ThroughAll, ThroughAllBoth),\n`both_directions`, `reverse_direction` and `draft_angle` have\ndefaults."
  2. Changed5 schema fields changedv1.5.0
    • changedInput schema / properties / input_data / description
      Previous value: -"Depth, direction and draft parameters."New value: +"Depth, direction, draft, and\noptional sketch_name parameters."
    • addedInput schema / properties / input_data / properties / both_directions
      Added value: +{
+  "default": false,
+  "description": "With end_condition 'ThroughAll', cut through the body both ways (same as 'ThroughAllBoth')",
+  "type": "boolean"
+}
    • changedInput schema / properties / input_data / properties / end_condition / description
      Previous value: -"End condition type"New value: +"'Blind' (cut 'depth' mm), 'ThroughAll' (through the body, one way) or 'ThroughAllBoth' (through the body both ways, for a sketch inside the body)"
    • changedInput schema / properties / input_data / properties / reverse_direction / description
      Previous value: -"Reverse cut direction"New value: +"Cut against the sketch normal instead of along it. Usually not needed: if the requested direction finds no material, the cut is retried the other way and the reply sets direction_flipped"
    • addedInput schema / properties / input_data / properties / sketch_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sketch to cut from, e.g. 'Sketch3'. If omitted, the sketch most recently created/exited in this session is used, but only if it still exists in the model — there is no other fallback. Pass this explicitly whenever more than one unconsumed sketch could exist, or after any operation that might have changed the active sketch."
+}
  3. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Well beyond the annotations: it declares the side effect (adds a Cut-Extrude feature), the auto-retry behavior with `direction_flipped`, the fail-loud ambiguity behavior, and the exact return payload including when `measured_change` is omitted. Annotations give only the safety profile (readOnlyHint=false), so this context is genuinely additive; cutting material is a modeled feature, not data destruction, so destructiveHint=false is not contradicted.

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?

Front-loads the operation in one line, then uses compact labeled segments (Needs/Changes/Returns) so an agent can scan prerequisites, effects, and outputs. No filler sentences; every clause carries operational information.

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?

Complete for a mutating modeling tool: prerequisites, post-conditions, failure modes, and return fields are all stated, and an output schema exists so return shape needn't be re-explained in depth. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds selection logic the schema does not: 'For a sketch inside the body, use ThroughAllBoth,' and the note that a one-way cut finding no material is retried and reported via `direction_flipped`. `depth` is not described beyond the schema, but the schema already labels it in millimeters.

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?

Specific verb+resource+scope: 'Cut material from the active part with a closed sketch profile: holes, slots, windows.' The material-removal framing cleanly separates it from the additive `create_extrusion` sibling, and the named examples make the intended geometry obvious.

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 sequencing ('Use it after `exit_sketch`'), an explicit rule for when to pass `sketch_name` versus relying on the just-closed sketch, an alternative-end-condition recommendation for sketches inside the body (ThroughAllBoth), and a prerequisite ('an open part with a solid body'). It also states what happens when doubt exists (an error naming the sketches found), which removes inference.

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