Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Extruded Cut

create_cut_extrude

Cut holes, slots, or windows from the active SolidWorks part using a closed sketch profile, choosing blind or through-all depth, optional draft angle, and bidirectional 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. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint false, destructiveHint false, idempotentHint false), so the bar is lower. The description still adds real behavioral context: the prerequisite of an open part with a solid body, the automatic retry in the opposite direction with direction_flipped set, and the error behavior when the sketch is ambiguous.

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 purpose is front-loaded and the remaining sentences are dense with useful rules rather than filler. The 'Returns:' sentence duplicates what the output schema already carries, which is the one stretch that does not fully earn its place.

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?

For a mutation tool with a nested input object and an output schema, the description covers prerequisites, sketch-selection fallback behavior, error conditions, direction retry, and an end-condition recommendation. An agent has everything needed to call it correctly without opening the schema.

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 per-parameter descriptions already explain depth, draft_angle, end_condition, both_directions and reverse_direction in detail. The description adds only marginal value on top of that, chiefly the retry-with-direction_flipped semantics and the ThroughAllBoth recommendation for sketches inside the body.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Cut material from the active part with a closed sketch profile') plus concrete examples (holes, slots, windows). It is clear what the tool produces, though it never explicitly contrasts itself with the neighboring create_extrusion or create_hole tools, so the agent must infer the boundary.

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 sequencing rule ('Use it after exit_sketch'), a clear rule for when to pass sketch_name, and a targeted recommendation ('For a sketch inside the body, use ThroughAllBoth'). It stops short of naming an alternative tool for cases where a cut is the wrong operation, so there is no when-not guidance.

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