Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

sheet_metal_base_flange

Creates the first sheet metal feature from a sketch: a closed profile becomes a flat plate, while an open line-and-arc chain becomes a bent profile extruded to depth with thickness and bend settings.

Instructions

Make the first feature of a sheet metal part from a sketch. A CLOSED sketch (a plate; holes allowed) becomes a flat plate of the given thickness. An OPEN sketch (one chain of lines and arcs) becomes a bent profile extruded to depth, its corners turning into bends. The sketch is the OUTSIDE of the part: the thickness is built inward. Refused when the part already has a base flange (a tab on a face comes later) or a solid body. Returns the thickness, bend radius, K-factor and number of bends read back from the part.

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": {
      "thickness": "<thickness>"
    },
    "name": "sheet_metal_base_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoClosed sketch: build the plate on the other side of the sketch plane. Open sketch: put the thickness on the other side of the profile
unitNoUnit for thickness, bend_radius and depth (mm, cm, m, inch or ft)
depthNoLength of an open profile (required for an open sketch, refused for a closed one)
sketchNoName of the sketch (default: the last sketch)
k_factorNoK-factor from 0 to 1
thicknessYesSheet thickness
bend_radiusNoInside bend radius (default: the thickness)

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?

With no annotations supplied, the description carries the full burden and does most of it: it discloses the geometric convention that the sketch is the OUTSIDE and thickness builds inward, both refusal conditions, and what is returned (thickness, bend radius, K-factor, bend count). It does not discuss permissions, engine state, or whether a failed attempt leaves the part untouched, so a small gap remains.

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?

Dense but front-loaded: purpose first, then the closed/open split, then the refusal conditions, then the return values. Every sentence carries information; the parenthetical asides ("a plate; holes allowed", "a tab on a face comes later") earn their place as disambiguators, though the prose is packed enough that an agent must read all of it.

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?

No output schema exists, so the description usefully names the returned values, and it covers the geometry and refusal semantics for a 7-parameter feature-creation tool. The only shortfall is operational context around failure recovery and document state, which is not addressed.

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 schema already documents each parameter, and the baseline is 3. The description still adds real meaning beyond it by tying `depth` to the open-sketch case (required there, refused for a closed sketch) and by explaining how sketch topology governs the thickness/flip interpretation rather than treating them as free-standing numbers.

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 ("Make the first feature of a sheet metal part from a sketch") and immediately splits the behavior into two recognizable cases (closed sketch = flat plate, open sketch = bent profile extruded to depth). It also distinguishes itself from the sibling `tab` by noting a tab on a face comes later, so an agent can tell the tools apart without opening either schema.

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 when-to-use conditions tied to sketch topology (closed vs open, holes allowed) and explicit when-not conditions: refused when the part already has a base flange or a solid body, with a pointer that a face tab comes later. Preconditions are concrete enough to check before calling.

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