Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

loft

Create a solid by connecting two or more closed profile sketches on different planes in the order given; optionally remove the formed volume as a cut.

Instructions

Loft a solid through two or more closed profile sketches on different planes, in the order given. By default the last two sketches are used. With cut=true the lofted 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": "loft"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutNoRemove material (a lofted cut) instead of adding it
mergeNoMerge new material into the body it touches (boss only)
profilesNoSketch names in loft order, e.g. ['Sketch2', 'Sketch3']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals the default profile selection, the boss-vs-cut semantics, and two concrete failure conditions (no solid body, cut removes nothing). It leaves out surrounding state requirements such as needing an active document or what happens with open profiles.

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?

Three tight sentences with zero filler: core operation first, default behavior second, the cut variant and its guard conditions last. Every clause carries operational information.

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 three-parameter, all-optional modeling tool with no annotations and no output schema, the description covers the decision-relevant behavior well. A brief note on where the resulting body lands (new body vs merged) or document prerequisites would close the remaining gap.

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

Parameters3/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. The description does add real meaning beyond the schema — profile ordering and the default when 'profiles' is omitted, plus cut-mode refusal conditions — but merge behavior is only covered by the schema, not elaborated here.

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 ('Loft a solid') plus the governing constraint ('two or more closed profile sketches on different planes, in the order given'), which is enough for an agent to distinguish this from other modeling operations 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?

Clearly frames the default case ('the last two sketches are used') and the alternate mode ('With cut=true the lofted volume is removed from the body instead'), including the preconditions under which the cut is refused. It stops short of naming sibling tools or explicitly saying when not to loft at all.

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