Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_swept_profile

Sweep a closed profile along a 2D path to model rails, gaskets, trims, or channels. Apply bend and corner radii, then get mass properties.

Instructions

Sweep an arbitrary closed PROFILE (cross-section) along a 2D PATH.

profile_mm = [[u,v],…] in mm: the closed cross-section on the Right plane (u → world -Z, v → world +Y), centred near the origin. path_mm = [[x,y],…] in mm on the Front plane — MUST start at the origin heading +X (the profile is perpendicular to the path there). Path corners are rounded with bend_radius_mm; corner_radii_mm rounds the profile's corners as for add_extruded_profile. Volume = profile_area · path_length. For non-round extrusions along a path (rails, gaskets, trim, channels). Returns mass properties. Use new_part first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSweep
path_mmYes
profile_mmYes
bend_radius_mmNo
corner_radii_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: hard constraints on the input ('MUST start at the origin heading +X', profile perpendicular there), the body it creates, the volume relation, and the return value ('Returns mass properties'). It omits failure modes and whether the sweep is additive/merges with existing bodies, so not a full 5.

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 capability and its use cases are front-loaded, and the dense notation is justified by the geometry it encodes. The parenthetical coordinate mapping is information-heavy but not padded; slightly telegraphic for a first read.

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 5-param geometry tool with no annotations and no output schema, it covers geometry conventions, constraints, rounding behaviour, and a return-value note, plus the ordering prerequisite. Remaining gaps (typical error cases, how the new body interacts with existing ones) are moderate but not blocking.

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 description coverage is 0%, so the description must compensate, and it largely does: profile_mm and path_mm orientations, planes, coordinate mappings, and units are given, and bend_radius_mm / corner_radii_mm are explained in terms of the behaviour they change. Only 'name' is left unaddressed, which is self-evident.

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 an arbitrary closed PROFILE along a 2D PATH') and then scopes it with concrete use cases (rails, gaskets, trim, channels) that separate it from the sibling add_swept_pipe (round pipe) and swept_region. An agent can pick this tool without opening the 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?

Explicitly says when to use it ('For non-round extrusions along a path') and gives a prerequisite ('Use new_part first'). It implies rather than names the alternative (add_swept_pipe for round sections), so no exclusion rule is spelled out, keeping it short of 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