Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Edge Flange

add_edge_flange

Adds a flange to a selected edge of a sheet-metal part at a specified length and angle. Pick the edge by point; requires an existing sheet-metal part.

Instructions

Add a flange to one edge of a sheet-metal part, at a length and angle.

Pick the edge with a point on it in mm (edge_point), e.g. on the top face's long edge. length is measured from that edge, so on a 2 mm sheet a 20 mm flange stands 22 mm above the bottom face. It fails when the volume doesn't change. Needs: a sheet-metal part (create_base_flange first). Changes: adds an Edge-Flange feature. Returns: flange with name, edge_length_mm (to check the pick) and volume_change (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": "add_edge_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe flange. `edge_point` ([x, y, z] mm) and `length` (mm) are required; `angle` is 90 and the bend radius the sheet's.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it is a non-readonly, non-idempotent, non-destructive write; the description adds what is mutated ('adds an Edge-Flange feature') and the failure mode tied to volume change. It leaves the non-idempotency unexplained (whether repeating the call stacks another flange), which is the one behavioral question an agent would still have.

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 verb and resource lead, followed by short labelled lines for pick, semantics, prerequisites, changes and returns. No sentence is filler; even the dimensional example carries real disambiguation value.

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 nested-parameter mutation tool it covers prerequisite, pick guidance, length semantics, failure mode and the resulting feature, and an output schema exists so return values need not be spelled out again. Minor gap: no explicit statement about repeated invocation behavior despite idempotentHint=false.

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 adds genuine meaning: edge_point is a point lying on the chosen edge in mm, and length is measured from that edge, illustrated by the 2 mm sheet / 20 mm flange / 22 mm overall height example. That resolves the ambiguity of where length starts, which the schema alone does not.

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 ('Add a flange to one edge of a sheet-metal part') plus the two governing parameters (length, angle). It also implicitly separates itself from create_base_flange by naming that tool as the prerequisite rather than an equivalent.

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 an explicit prerequisite ('Needs: a sheet-metal part (`create_base_flange` first)') and a concrete failure condition ('It fails when the volume doesn't change'), which steers the agent on both ordering and diagnosis. It does not say when to choose another flange or sheet-metal feature instead, so it stops short of full alternative routing.

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