Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Base Flange

create_base_flange

Creates a sheet-metal base flange from a sketch with specified thickness, bend radius, and K-factor, forming the first feature for flat or bent sheet-metal parts.

Instructions

Start a sheet-metal part: a base flange from a sketch, with its thickness, bend radius and K-factor.

A closed sketch (a rectangle) makes a flat plate; an open one (a line or an L) makes a bent profile extruded by depth. Use it as a sheet-metal part's first feature, then add_edge_flange, create_sketched_bend and set_flat_pattern; export the blank with export_flat_pattern. The values are read back from the feature. Needs: an open part with the profile sketch closed. Changes: adds a Base-Flange feature and makes the part sheet metal. Returns: flange with name, thickness_mm, bend_radius_mm, k_factor and volume_after (mm³).

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_base_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe flange. `thickness` and `bend_radius` (mm) are required; `k_factor` is 0.5; `depth` only for an open profile.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) it discloses the concrete effect ('adds a Base-Flange feature and makes the part sheet metal') and the prerequisite document state, which is exactly the kind of context annotations cannot carry. It stops short of describing failure behavior (e.g. what happens if the part is already sheet metal) or how `depth` errors surface for a closed profile, so it is strong but not exhaustive.

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 purpose is front-loaded and the Needs/Changes/Returns labels make the remaining content scannable. However, the prose runs on in long clauses (the closed/open sketch sentence spans lines) and repeats the required parameters that the schema already marks required, adding mild redundancy.

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?

For a feature-creating mutation with a nested input object, it covers all three things an agent needs: preconditions, side effects, and return shape. It even summarizes the `flange` return fields, which is generous given an output schema exists.

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 earns above that by explaining the semantic coupling the schema only implies — that a closed sketch (rectangle) yields a flat plate while an open sketch (line or L) is extruded by `depth`. It does not add detail on `reverse` or `k_factor` beyond the schema defaults, so it is not a full 5.

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 ('Start a sheet-metal part: a base flange from a sketch') and immediately defines its two modes — a closed sketch making a flat plate versus an open profile making a bent profile extruded by `depth`. It is clearly distinguishable from `add_edge_flange`, `create_sketched_bend`, and `create_extrusion` because it is framed as the sheet-metal part's first feature.

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?

Gives explicit positioning ('Use it as a sheet-metal part's first feature, then `add_edge_flange`, `create_sketched_bend` and `set_flat_pattern`; export the blank with `export_flat_pattern`'), which names downstream alternatives and their ordering. It also states the precondition ('an open part with the profile sketch closed'), so the agent knows when it can and cannot be called.

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