Skip to main content
Glama

revolve_sketch

Revolve a closed sketch around an axis to model turned parts like shafts, bushings, and flanges. Specify axis, angle, direction, and merge settings.

Instructions

Revolución (saliente por revolución) — revolve a closed sketch around an axis. The standard SolidWorks workflow for turned parts: flechas (shafts), bujes (bushings), bridas (flanges), finiales, insertos torneados — anything spun on a lathe.

Args: axis_name: Name of the axis to revolve around. Pass the "Eje1" name returned by create_reference_axis (typically the intersection of two default planes through the part origin). The axis must lie in the same plane as — or beside — the sketch profile. Profiles that cross the axis raise a SW geometry error. angle_deg: Sweep angle in degrees, in the open interval (0, 360]. Default 360 (revolución completa) covers the standard turned- part case. Partial angles (e.g. 180) are useful for sectores, half-housings, leva-cams. reverse_direction: Flip rotation sense around the axis. Default follows SW's natural sense; flip if the resulting body comes out on the wrong side of the sketch plane. merge: True (default) merges with existing solid material it touches. False keeps the revolve as a separate body (multi-body modeling).

Returns the new Revolución feature (type=boss_revolve, D1=angle_deg).

Caveat: D1 is the sweep ANGLE, not a distance. modify_dimension can update D1 to retune the angle, but the sketch profile dimensions (the turned silhouette itself) are NOT parametric in v1 — same caveat as extrude_sketch (sketch primitives are draw-once-only; resize requires a fresh rebuild).

Example — Ø50mm × 10mm thick disc, full revolution around the Z axis: eje = create_reference_axis("front", reference_2="right") create_sketch("top") create_line(0, 0, 25, 0) # half-radius along +X create_line(25, 0, 25, 10) # thickness along +Y create_line(25, 10, 0, 10) # back-radius create_line(0, 10, 0, 0) # close on the axis revolve_sketch(eje["name"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mergeNo
angle_degNo
axis_nameYes
reverse_directionNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: axis constraints, error conditions, merge behavior, return type (boss_revolve), D1 meaning, and a caveat about sketch parametric limitations.

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 description is front-loaded with purpose and includes a useful example. It is slightly verbose with bilingual repetition and parameter explanations that could be more terse, but every sentence adds value.

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?

Given no output schema, the description covers return type (boss_revolve), key dimension D1, and a critical caveat about non-parametric sketch dimensions. The example and parameter details make it fully complete for a 4-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description explains all four parameters in detail: axis_name with acquisition and constraints, angle_deg with range and examples, reverse_direction with impact, and merge with multi-body implications.

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 clearly states the tool revolves a closed sketch around an axis, and provides a list of typical turned parts (shafts, bushings, flanges, etc.), distinguishing it from sibling tools like extrude_sketch or revolve_cut.

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?

The description explains when to use (turned parts, full vs partial revolutions) and includes a caveat about axis placement and profile crossing. It does not explicitly exclude alternatives, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server