Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

sketched_bend

Bends sheet metal along one sketch line on a flat face, setting angle, radius, side, and bend position.

Instructions

Bend sheet metal along the single line of a sketch on its flat face, toward the sketch's side (reverse bends the other way). SolidWorks chooses the side that stays; fixed_point in the result is on it. position: centerline (the line is the middle of the bend), inside, outside or bend_outside. Refused while flattened.

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": {
      "sketch": "<sketch>",
      "angle": "<angle>"
    },
    "name": "sketched_bend"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
angleYesBend angle in degrees (1-179)
radiusNoBend radius (default: the part's)
sketchYesName of a sketch with one line, on a flat face of the sheet
reverseNoBend away from the sketch's side
positionNoWhere the bend sits on the linecenterline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose non-obvious behavior: bend direction defaults toward the sketch side, reverse flips it, SolidWorks chooses the retained side, and fixed_point lands on it. It stops short of describing failure modes beyond the flattened state or whether the sketch/feature is consumed.

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?

The text is dense and front-loaded, opening with the core action and direction semantics. The clause about fixed_point in the result is slightly cryptic without an output schema, but overall there is little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation with no annotations and no output schema, the description covers the key bend semantics and the flattened refusal well. However, it leaves the result shape, error behavior beyond flattening, and whether the sketch is consumed or the bend becomes a feature unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all six parameters. The description adds some meaning by explaining that centerline places the line in the middle of the bend and that reverse bends the other way, but inside, outside, and bend_outside remain unexplained.

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 states a specific verb and resource ('Bend sheet metal') and adds the precise scope ('along the single line of a sketch on its flat face'). It distinguishes the operation from sheet-metal conversion or sketch creation without needing to name siblings.

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?

It provides a clear prerequisite (a sketch with one line on a flat face) and an explicit refusal condition ('Refused while flattened'). It does not name alternative tools for related sheet-metal operations, but the context and exclusion are strong enough to guide selection.

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