Skip to main content
Glama
solidworks-mcp

solidworks-mcp

base_flange

Creates a sheet metal flange from the last sketch: an open line chain becomes a bent extruded sheet, while a closed profile becomes a flat tab, adding Sheet-Metal and Flat-Pattern features.

Instructions

Creates a sheet metal base flange from the last sketch (the one open, or the last closed one): an open chain of lines gives a bent sheet extruded depth_mm, a closed profile gives a flat tab. Adds the Sheet-Metal and Flat-Pattern features to the tree. The sheet grows on one side of the sketch lines (the other with reverse_thickness=True).

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

Input Schema

NameRequiredDescriptionDefault
depth_mmNoExtrusion depth in mm for open sketch profiles
thickness_mmNoSheet metal thickness in mm
bend_radius_mmNoInternal bend radius in mm
reverse_thicknessNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare this as a non-read-only, non-destructive, non-idempotent operation, and the description adds real substance on top: it discloses that Sheet-Metal and Flat-Pattern features are inserted into the tree and that thickness grows to one side of the sketch lines, reversible via reverse_thickness. It stops short of describing failure modes such as having no sketch available or repeated invocation behavior.

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?

Roughly four clauses, all load-bearing, with the sketch-source rule stated first and the conditional outcomes immediately after. No filler or restatement of the tool name.

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?

With an output schema present, the description need not explain return values, and it covers sketch source, geometric outcome, feature-tree side effects, and thickness direction. The remaining gap is preconditions and error behavior for a mutation tool that requires an existing sketch in an active document.

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 75%, so the schema already explains depth_mm, thickness_mm and bend_radius_mm. The description earns credit by supplying the meaning of the only undocumented parameter, reverse_thickness, in terms of which side of the sketch the material grows on, and by tying depth_mm to the open-profile case.

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 names a specific verb and resource ('Creates a sheet metal base flange from the last sketch') and then branches on the decisive input condition: an open chain yields a bent extruded sheet, a closed profile yields a flat tab. That behavioral split distinguishes it from generic siblings like extrude or edge_flange without needing to name them.

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?

Usage context is implied through the sketch-selection rule ('the one open, or the last closed one'), which tells the agent what state must exist first. However, there is no explicit when-to-use versus when-not guidance and no named alternative such as edge_flange for adding a flange to an existing wall.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.