Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Draft Faces

add_draft

Drafts selected faces of an active part by a specified angle around a neutral face, adding a Draft feature for moulded-part geometry.

Instructions

Draft faces of the active part by an angle, e.g. for a moulded part.

Pick each face to draft and the neutral face it pivots on (usually the parting or bottom face) with a point on each (mm). It fails when the volume doesn't change. Needs: an open part. Changes: adds a Draft feature. Returns: draft with name, angle, faces_drafted, and volume_before, volume_after and volume_change (mm³).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe draft. `angle` (degrees, under 90), `faces` (at least one point) and `neutral_face` (a point) are required.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds genuinely new behavioral data: the precondition of an open part, the failure mode when volume is unchanged, and that the operation adds a persistent Draft feature to the model. It stops short of saying whether the feature can be edited or removed afterward.

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 definition is front-loaded with the action, followed by selection guidance, prerequisites, and effects, in a compact block with no filler. The Returns sentence partly duplicates the output schema but is short enough not to be wasteful.

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 geometry-mutating feature tool with a nested input object and an output schema, the description covers what is required, what it modifies, and the primary failure mode. The return values are already in the output schema, so spelling them out is redundant rather than missing information.

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 every parameter (angle, faces, reverse, neutral_face) is already documented with units and constraints, making 3 the baseline. The description's phrasing 'with a point on each (mm)' and 'the neutral face it pivots on' reinforces the point-based selection model but adds little the schema does not already say.

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 description opens with a specific verb and resource ('Draft faces of the active part by an angle') and gives a canonical use case ('e.g. for a moulded part'). This clearly separates it from sibling feature-adders such as add_fillet or add_chamfer, though it does not explicitly name an alternative.

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?

Guidance goes beyond stating the purpose: it tells the agent to pick faces plus a neutral face ('usually the parting or bottom face'), states prerequisites ('Needs: an open part'), and gives a failure condition ('It fails when the volume doesn't change'). There is no explicit routing to a sibling tool for adjacent cases, which keeps this below a 5.

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