Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

convert_to_sheet_metal

Converts a solid part into sheet metal by defining a fixed face, bend edges, and thickness, then verifies the flat pattern is a single piece and returns bend and flat-pattern data.

Instructions

Turn the solid body of a part into sheet metal with SolidWorks' Convert to Sheet Metal: give fixed_face (a point on the face that stays fixed), bend_edges (a point on each edge that becomes a bend) and thickness; SolidWorks adds the rips itself. The result is checked by measuring the flat pattern (one piece), and what was made is removed again when that fails. Returns thickness, bend radius, K-factor and flat pattern size. Insert Bends on a shelled part is not offered.

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": {
      "fixed_face": "<fixed_face>"
    },
    "name": "convert_to_sheet_metal"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoPut the thickness on the other side
unitNoUnit for the coordinates, thickness and bend_radius (mm, cm, m, inch or ft)
methodNoconvert = Convert to Sheet Metal on a solid (the only method)convert
k_factorNoK-factor from 0 to 1
thicknessNoSheet thickness (required)
bend_edgesNoA point on each edge that becomes a bend
fixed_faceYes
bend_radiusNoInside bend radius (default: the thickness)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so well: it discloses that SolidWorks adds the rips itself, that the result is validated by measuring the flat pattern, and that the created feature is removed again if validation fails. That failure-and-rollback behavior is exactly the kind of context an agent cannot get from the schema.

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?

Three dense sentences, front-loaded with the verb and resource, then parameters, then validation behavior and return values. The parentheticals are efficient rather than padded, though the run-on second sentence packs a lot and could be split.

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 an 8-parameter mutation with no output schema, the description covers preconditions, mechanics, failure handling, and the shape of the return value (thickness, bend radius, K-factor, flat pattern size). Nothing essential for correct invocation is 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 88%, so the baseline is 3, but the description earns more: it explains that fixed_face is a point on the face that stays fixed and bend_edges is a point on each edge that becomes a bend, semantics the schema leaves thin for these nested objects. It also notes thickness is required and outputs bend radius and K-factor, though it does not cover unit, flip, or method.

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?

Names the specific operation ('Convert to Sheet Metal') on a specific resource (the solid body of a part) and even scopes it against the omitted alternative ('Insert Bends on a shelled part is not offered'). An agent can tell immediately this converts an existing solid rather than creating a base flange.

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?

States the precondition (the part must have a solid body) and the exclusion (Insert Bends on a shelled part is not offered), which steers the agent away from a wrong approach. It stops short of naming a sibling tool to use instead for the shelled-part case.

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