Skip to main content
Glama

sweep_sketch

Create a boss feature by sweeping a closed profile sketch along a path, ideal for generating tubes, gaskets, or weld beads.

Instructions

Barrido (sweep) — sweep a closed profile sketch along a path sketch to make a boss feature.

Standard autoparts use: tubos (tubes / pipes following a curved path), juntas / empaques (gaskets — closed-loop path), guías de cable (cable routes), cordones de soldadura (weld beads along an edge), perfiles extruidos curvos.

Args: profile_sketch_name: Name of the CLOSED profile sketch (e.g. 'Croquis1' for a circle to make a tube). Created via create_sketch + create_circle / create_rectangle / etc. Must be a closed contour. path_sketch_name: Name of the PATH sketch (e.g. 'Croquis2' for the route the profile follows). Open or closed paths both work. Created via create_sketch + create_line / create_arc / etc. on a plane perpendicular (or tangent) to the profile's plane at the path start. merge: True (default) merges with existing solid material it touches. False keeps the swept body separate (multi-body).

Returns Feature (name='Barrido{n}', type='boss_sweep', dimensions={}). Sweeps don't have parametric D1/D2 in v1 — the geometry is fully driven by the two sketches.

Caveat (v1): the two sketches must already exist as separate features in the tree. Profile and path can't be the same sketch. Advanced options (twist, guide curves, thin-feature, circular- profile shortcut) are NOT exposed in v1; defaults are: follow- path orientation, no twist, no guide curves.

Example — Ø6mm tube along an L-shaped path: # Profile: 6mm-radius circle on Front plane at origin create_sketch('front') create_circle(0, 0, 3) # Croquis1 # Path: L-shape on Top plane create_sketch('top') create_line(0, 0, 0, 50) create_line(0, 50, 50, 50) # Croquis2 sweep_sketch('Croquis1', 'Croquis2')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mergeNo
path_sketch_nameYes
profile_sketch_nameYes
Behavior5/5

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

Despite no annotations, the description fully discloses behavioral traits: merge parameter behavior, non-parametric nature (no D1/D2), orientation defaults (follow-path, no twist/guide curves), and v1 limitations. No contradiction with missing annotations.

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?

Well-structured with summary, args, returns, caveats, and example. Front-loaded purpose. Slightly verbose (example code is redundant with text) but still efficient. Minor deduction for unnecessary repetition.

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 and missing annotations, the description covers return value (Feature object), v1 limitations, and complete usage context. No gaps remain for an agent to invoke correctly.

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?

With 0% schema description coverage, the description fully explains all three parameters: profile_sketch_name must be closed, path_sketch_name can be open/closed and perpendicular plane, merge merges or keeps separate. Adds critical context beyond 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?

Clearly states it sweeps a closed profile sketch along a path to create a boss feature. Distinguishes from sibling tools like extrude_sketch and revolve_sketch by specifying the sweep operation, and mentions sweep_cut for cutting vs. boss.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit prerequisites (sketches must exist, cannot be same sketch), limitations (no advanced options), and concrete examples of standard autoparts use cases. Also includes a code example and default behavior.

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