Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

cut_extrude

Cuts the most recent sketch through a SOLIDWORKS body to remove material and reports the removed volume, reversing direction automatically if the first cut removes nothing.

Instructions

Cut the most recent sketch through the body to remove material. Reports the volume removed. If the requested direction removes nothing (for example a sketch lying beside the body), the other direction is used and the result says so. A sketch that already belongs to a feature is not cut again: draw a new sketch first.

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

Input Schema

NameRequiredDescriptionDefault
flipNoCut in the opposite direction
unitNomm, cm, m, inch or ft
depthNoCut depth (total depth for mid_plane; ignored for through_all)
through_allNoLegacy: same as end_condition='through_all'
end_conditionNoblind = to depth; through_all = through the whole body in one direction; through_all_both = both directions; mid_plane = depth split equally both sides of the sketchblind
both_directionsNoLegacy: with through_all = through_all_both, otherwise mid_plane

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the automatic fallback to the opposite direction when the requested direction removes nothing, says the result reports this, and explains that sketches already consumed by a feature are not cut again. It stops short of stating irreversibility or permission requirements for a destructive modeling operation.

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?

The description is four tight sentences, front-loaded with the core action, followed by the direction fallback and sketch prerequisite. Every sentence contributes operational value without repetition.

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?

For a six-parameter CAD mutation tool with no output schema, the description covers the core action, return-value reporting, direction fallback behavior, and sketch reuse constraint. It is nearly complete, though it could mention units or failure modes more explicitly.

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 parameters such as depth, end_condition, flip, and legacy flags are already documented in the schema. The description reinforces the direction and sketch-selection context but adds no syntax or constraints beyond what the schema provides.

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?

The description states a specific verb and resource: cutting the most recent sketch through the body to remove material, and notes that it reports the volume removed. This distinguishes it from additive extrusion siblings such as extrude_sketch and extrude_surface.

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?

It clearly establishes the operating context: cut the most recent sketch through the body, and draw a new sketch first if the existing sketch already belongs to a feature. It does not explicitly compare against sibling extrusion tools, so it falls short of full when-to-use/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