Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Sketched Bend

create_sketched_bend

Bends a sheet-metal part along a line sketched on one of its faces. Use it to add a Sketched Bend feature with a set angle, radius, and direction.

Instructions

Bend a sheet-metal part along a line sketched on one of its faces.

Sketch a line across a face of the sheet (create_sketch with face_point, then add_line), close the sketch, then call this. SolidWorks chooses which side of the line stays put; the reply's bounding_box_mm shows which side moved, and reverse bends the other way. Needs: a sheet-metal part and the bend-line sketch. Changes: adds a Sketched Bend feature. Returns: bend with name and bounding_box_mm.

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": "create_sketched_bend"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: `angle` is 90, the bend radius the sheet's, and the sketch the last closed one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, so the description adds genuine extra context: SolidWorks decides which side of the line stays fixed, the reply's bounding_box_mm reveals which side moved, and reverse flips it. It also states the effect ('adds a Sketched Bend feature'). Missing only details like whether it can fail on non-sheet-metal bodies or on invalid sketch geometry.

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?

Front-loaded purpose sentence, then compact labels for prerequisites, effects, and returns. Every sentence carries information — the sketch-creation recipe, the side-selection caveat, and the return shape — with no filler.

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 zero-required-parameter mutation with an output schema, the description covers the prerequisite chain, the ambiguity the caller must resolve via reverse, the state change, and the return fields. Nothing an agent needs to invoke it correctly appears to be missing.

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 more by explaining that the default side choice is not under the caller's control, which is what makes 'reverse' meaningful rather than circular as the schema's 'Bend the other way' implies. It also reinforces that angle, radius, and sketch all have defaults.

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 — 'Bend a sheet-metal part along a line sketched on one of its faces' — which is unambiguous and clearly distinct from the other create_* siblings. The first sentence alone lets an agent decide relevance 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?

Gives an explicit prerequisite workflow (create_sketch with face_point, then add_line, close the sketch, then call this) and required state (a sheet-metal part plus the bend-line sketch). It doesn't name any alternative or when-not condition, but the sequencing guidance is concrete and actionable.

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