Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Loft

create_loft

Creates a solid loft through two or more ordered closed profile sketches, enabling shapes that change cross-section such as wings or transition ducts.

Instructions

Loft a solid through two or more closed profile sketches, in order (Insert > Boss/Base > Loft).

Use it for shapes that change section, such as a wing or a transition duct. Put each profile on its own plane (see create_reference_plane). Needs: an open part with the profile sketches. Changes: adds a Loft feature. Returns: loft with name, profiles and guide_curves.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_data": "<input_data>"
    },
    "name": "create_loft"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe loft. `profiles` (sketch names, in order) is required; `guide_curves`, `start_tangent`, `end_tangent` and `merge_result` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Beyond the annotations, the description adds meaningful behavior: it adds a Loft feature, requires an open part and closed profile sketches, and emphasizes profile order. It does not discuss failure behavior, reversibility, or non-idempotency, but annotations already cover read-only and destructive hints.

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?

The description is front-loaded and well structured, moving from purpose to use case, prerequisites, side effects, and return value. The 'Needs / Changes / Returns' phrasing is efficient and easy to scan. Every sentence adds relevant information.

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 the tool's complexity, nested input schema, annotations, and output schema, the description provides enough context to call it correctly. It covers purpose, prerequisites, profile ordering, side effects, and return value. Remaining parameter details are handled by the fully documented schema.

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. The description adds important semantics beyond the schema by specifying that profiles must be closed, two or more, and ordered, and that each profile should be on its own plane. It does not explain guide curves, tangents, or merge_result, but the schema documents those.

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?

The description states a specific verb and resource: 'Loft a solid through two or more closed profile sketches, in order.' It also clarifies the shape type it is for, such as a wing or transition duct. It does not explicitly contrast with sibling operations like sweep or extrusion, so it is clear but not fully sibling-differentiated.

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?

It gives clear usage context: use it for shapes that change section, and it lists prerequisites such as an open part with profile sketches and each profile on its own plane. It references create_reference_plane for plane creation. It does not state when not to use it or name alternative modeling operations.

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