Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_loft

Loft solid between multiple profile sketches with optional guide curves and tangency control.

Instructions

Loft a solid between two or more profile sketches.

Creates a lofted boss/protrusion (Insert > Boss/Base > Loft) blending the listed profile sketches in order. Each profile must be a closed contour. Optional guide curves shape the transition between profiles.

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_dataYesProfile names, optional guide curves, and tangency/merge options.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses that each profile must be a closed contour and that guide curves are optional, but does not explain other behavioral aspects like error handling, effect of merge_result, or what happens with invalid inputs. Some important details are missing.

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 description is three sentences, front-loaded with the main purpose. It is concise, but the inclusion of the menu path 'Insert > Boss/Base > Loft' is somewhat redundant for an AI agent. Overall efficient with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a loft operation and the nested schema with five parameters, the description covers the main purpose and the closed-contour constraint but omits details about other parameters like merge_result, start_tangent, and end_tangent. The output schema is present (not shown) but does not compensate for these gaps.

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 baseline is 3. The description adds value by stating 'Each profile must be a closed contour', which is a constraint not in the schema, and clarifies that guide curves shape the transition. However, it does not elaborate on other parameters like merge_result or tangent conditions.

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?

The description clearly states 'Loft a solid between two or more profile sketches' and 'Creates a lofted boss/protrusion', using a specific verb and resource. It distinguishes from sibling tools like create_extrusion, create_revolve, etc., by emphasizing multiple profiles and optional guide curves.

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

Usage Guidelines3/5

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

The description implies usage for blending profiles but provides no explicit guidance on when to use this tool versus alternatives (e.g., when not to use it). It does not mention exclusions or provide comparisons to sibling tools like create_extrusion or create_sweep.

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