Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Revolve

create_revolve

Revolves a closed sketch or profile around a reference axis or centerline to add a solid revolve feature to the active part, enabling shafts, knobs, and other turned shapes.

Instructions

Revolve a closed sketch around an axis, adding a solid to the active part.

Use it for turned shapes (shafts, knobs). It revolves the sketch sketch_name names, or the one exit_sketch closed last, about the reference axis axis_entity names (from create_axis), or about the centreline drawn in the sketch with add_centerline. A sketch or axis that isn't in the model fails before anything is built. Needs: an open part and a closed profile with a centreline or a reference axis. Changes: adds a Revolve feature. Returns: revolve (name, sketch and axis_entity when named, angle) 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_revolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe revolve. `angle` (degrees, 360 for a full turn) is required; `sketch_name`, `axis_entity`, `both_directions`, `reverse_direction`, `thin_feature` and `merge_result` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-readonly, non-destructive, non-idempotent mutation, and the description earns credit for adding atomicity ("fails before anything is built") and stating that a Revolve feature is appended. It does not explain what `merge_result=true` does to bodies already in the part, which is the main behavioural risk for a feature that must fuse with existing geometry.

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 Needs/Changes/Returns structure is efficient and front-loaded, with the shape-use sentence placed before the mechanics. A few clauses (e.g. re-listing which parameters have defaults) duplicate the schema and could be dropped.

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?

An output schema exists, yet the description still summarizes the returned `revolve` and `measured_change` payloads succinctly. With prerequisites, failure mode and axis/sketch resolution all covered, only the merge-into-existing-geometry behaviour is left implicit.

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 `angle`, `axis_entity`, `sketch_name` and the boolean flags are already documented in the schema. The description mostly restates the fallback rules and confirms that several flags are optional with defaults, adding little meaning beyond the structured fields.

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?

"Revolve a closed sketch around an axis, adding a solid to the active part" names a specific verb, resource and result. The follow-up "Use it for turned shapes (shafts, knobs)" effectively separates it from create_extrusion, create_sweep and create_loft without opening any schema.

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 positive selection criteria (turned shapes) and hard prerequisites (open part, closed profile, centreline or reference axis), plus the exact fallback chain between `sketch_name`/`axis_entity` and `exit_sketch`/`add_centerline`. It stops short of saying when NOT to use it or naming the extrusion/loft tool as the alternative for non-turned shapes.

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