Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extrude_sketch

Extrude an existing sketch in a SolidWorks part by name, controlling depth or up-to face/point and merge direction, while preserving sketch dimensions and relations and returning mass properties.

Instructions

Extrude an existing sketch of the current part by name, e.g. one a person drew.

depth_mm along the sketch's normal (reverse=True: the other way), merged with the body. Or up_to='next': up to the next face of the part, ending on its shape (a post into a curved wall) and following it when it changes; or up_to='@x,y,z': up to the face through that point, also where 'next' fails (a side of the profile on a face: the refusal names a point ahead). The sketch keeps its own dimensions and relations, so the person's design stays in charge; read_sketch shows it first. Returns mass properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoExtrude
up_toNo
sketchYes
reverseNo
depth_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.13.0
    • addedInput schema / properties / depth_mm / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / depth_mm / default
      Added value: +null
    • removedInput schema / properties / depth_mm / type
      Removed value: -"number"
    • addedInput schema / properties / up_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Up To"
+}
    • changedInput schema / required
      Previous value: -[
-  "sketch",
-  "depth_mm"
-]New value: +[
+  "sketch"
+]
  2. Addedv0.9.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose real behavior: the result is merged with the body, the sketch keeps its dimensions/relations (a non-destructive claim about authored geometry), the return is mass properties, and it hints at failure semantics ('the refusal names a point ahead'). It omits whether the operation is purely additive and what preconditions (active part, valid sketch) apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a run-on of nested parentheticals and asides ('e.g. one a person drew', 'so the person's design stays in charge') that make the mode logic harder to scan than it needs to be. Information density is high, yet the structure could be tightened without losing content.

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 annotations, no output schema, and five undocumented parameters, the description supplies a lot: modes, direction, return value, and sketch preservation. It remains a bit short on preconditions and on the 'name' argument for a tool whose siblings imply richer feature-graph behavior.

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 0%, so the description must compensate, and it does well for three of five parameters: depth_mm is 'along the sketch's normal', reverse=True goes the other way, and up_to accepts 'next' or a '@x,y,z' point with distinct behaviors. The 'name' parameter (feature naming, default 'Extrude') is never explained, leaving one gap.

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?

The first sentence gives a specific verb+resource ('Extrude an existing sketch of the current part by name'), and the qualifier 'existing sketch' implicitly distinguishes it from siblings like add_extruded_profile that create new geometry. It does not name any sibling outright, so the differentiation is inferred rather than stated.

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 gives clear selection logic among modes: depth_mm along the normal, or up_to='next', or up_to='@x,y,z' when 'next' fails, plus the prerequisite 'read_sketch shows it first'. It never says when to prefer this tool over cut_sketch or add_extruded_profile, so the routing guidance is incomplete.

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