Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Sweep

create_sweep

Creates a solid by sweeping a closed profile sketch along an open path sketch, with optional twist angle and along-path twist for building swept boss features.

Instructions

Sweep a closed profile sketch along a path sketch to make a solid (Insert > Boss/Base > Sweep).

Draw the closed profile and the open path as two sketches first. The profile is the sketch you closed last that isn't the path. Needs: an open part with both sketches. Changes: adds a Sweep feature. Returns: sweep with name, path, twist_along_path and twist_angle.

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_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe sweep. `path` (the path sketch's name) is required; `twist_along_path`, `twist_angle` (degrees) and `merge_result` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-idempotent, non-destructive mutation, and the description adds real context beyond that: it creates a new Sweep feature in the tree and returns the `sweep` object with name, path, twist_along_path and twist_angle. It omits failure behavior and whether repeated calls stack duplicate features, which given idempotentHint=false would be worth stating.

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-loaded with the action and UI equivalent, then prerequisites, then effects, then return shape. Every sentence carries distinct information with no repetition of the schema.

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 feature-creation tool with an output schema and safety annotations already supplied, this description covers prerequisites, side effects, return payload and the non-obvious profile inference rule. Nothing an agent needs in order to invoke it 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 meaning the schema cannot express: the profile is not a parameter at all and is inferred as 'the sketch you closed last that isn't the path'. That implicit-selection rule is essential to calling the tool correctly. Twist and merge semantics are left entirely to the schema.

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?

States a specific verb and resource ('Sweep a closed profile sketch along a path sketch to make a solid') plus the equivalent UI path, which unambiguously separates it from sibling feature creators like create_extrusion, create_loft and create_revolve.

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 concrete preconditions: two sketches must exist, the profile must be closed and the path open, the part must be open. It does not name an alternative tool or say when a sweep is the wrong choice (e.g. vs. loft), so it stops short of full routing 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