Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_revolved_profile

Create a revolved solid or ring by spinning a closed profile on the Front plane around an axis in it. Use for shafts, vases, or rings; returns mass properties.

Instructions

Revolve a closed profile on the Front plane about an axis in it.

Without axis_mm: profile_mm = [[r, z], …] in mm, r = distance from the Y axis, z = position along it. With axis_mm = [[x1, y1], [x2, y2]]: profile_mm gives [x, y] points and the axis is the line through those two points, anywhere and at any angle (a hub turned about its own centre). Auto-closed and spun angle_deg (default 360°). Points on the axis give a solid (shafts, vases); a profile away from it gives a ring. The profile may not cross the axis. corner_radii_mm rounds corners as for add_extruded_profile (not those on the axis). Returns mass properties. Use new_part first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRevolve
axis_mmNo
angle_degNo
profile_mmYes
corner_radii_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / axis_mm
      Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Axis Mm"
+}
  2. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / corner_radii_mm
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Corner Radii Mm"
+}
  3. First observedv0.4.0

TDQS

A4.5/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 does well: it discloses the auto-close/spin behavior, the default 360° angle, the hard constraint that the profile may not cross the axis, and that it returns mass properties. It stops short of document-state requirements beyond 'use new_part first' or error behavior.

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?

Front-loaded with the core action, then builds geometry semantics in dense but useful sentences. Slightly long for a tool description, but nearly every clause carries information the schema cannot.

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?

Five parameters at 0% schema coverage and no output schema are fully accounted for: input formats, defaults, constraints, geometry outcomes and the returned mass properties are all stated, leaving nothing an agent needs missing.

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%, so the description must compensate, and it does: it specifies the two distinct profile_mm formats ([r,z] radial vs [x,y] absolute) tied to the presence of axis_mm, explains axis_mm as a two-point line, and notes angle_deg defaults and corner_radii_mm corner-only-on-profile behavior.

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 ('Revolve a closed profile on the Front plane about an axis in it'), and the geometry described (spun profile, axis semantics) clearly separates it from add_extruded_profile, add_swept_profile and add_lofted_solid.

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 clear selection context (points on the axis yield solids/shafts, an offset profile yields a ring) and a prerequisite ('Use new_part first'), but never names an alternative sibling or states when not to use this in favor of extrusion/sweep/loft.

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