Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

sweep

Create a solid along a path sketch from a closed profile or a specified diameter, and optionally remove the resulting volume as a cut.

Instructions

Sweep a solid along a path sketch. Give a closed profile sketch and a path sketch (the path must start on the profile's plane), or give a diameter to sweep a round bar along the path without a profile sketch. By default the profile is the last sketch and the path the one before it. With cut=true the swept volume is removed from the body instead (refused when the part has no solid body or the cut removes nothing).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutNoRemove material (a swept cut) instead of adding it
pathNoName of the path sketch (default: the sketch before the profile; the last sketch when diameter is given)
unitNoUnit for diameter (mm, cm, m, inch or ft)
mergeNoMerge new material into the body it touches (boss only)
profileNoName of the profile sketch (default: the last sketch)
diameterNoSweep a circle of this diameter instead of a profile sketch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does disclose non-obvious behavior: default sketch resolution for both profile and path, that cut removes swept volume rather than adding, and two explicit failure modes (no solid body, empty cut). It stops short of saying whether the operation is undoable, what feature/body state results, or whether an active document is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph ordered by importance: core action, the two modes, the defaults, then the cut exception. Every clause adds information an agent needs, and nothing is redundant with the parameter schema.

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 six-parameter, all-optional modeling operation with no annotations and no output schema, the description covers mode selection, defaults, preconditions, and failure behavior. The remaining gap is scope context (active document/part requirement) and any indication of what the call produces on success.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the interaction between profile and path defaults ('the last sketch' and 'the one before it') and the fact that supplying diameter replaces the profile sketch entirely. The unit and merge parameters are left to their schema text, which is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Sweep a solid along a path sketch') and immediately branches into the two supported modes: profile-sketch sweep and diameter-based round-bar sweep. It is clearly not a pattern, chamfer, or extrude operation, though it never names a related alternative tool to contrast against.

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 concrete selection criteria between the two modes ('give a closed profile sketch and a path sketch... or give a diameter') plus the defaults that apply when the caller passes nothing. It also states a precondition ('the path must start on the profile's plane') and the conditions under which cut is refused, but does not point to any alternative tool for cases this one cannot handle.

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