Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

edge_flange

Adds a bent-up wall to a sheet metal edge through a selected point, with flange length measured to the outer virtual sharp and position options inside, outside, or bend outside.

Instructions

Add an edge flange (a wall bent up) on the sheet metal edge through a point, with its length measured to the outer virtual sharp. position: inside (outer face on the edge), outside (inner face on the edge) or bend_outside (bend outside the edge). Returns the volume added, the flat size and what defining its profile sketch added (added_by_solidworks, relations_added: SolidWorks', not from your spec). 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": {
      "edge": "<edge>",
      "length": "<length>"
    },
    "name": "edge_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeYesA point on the edge (within 0.5 mm)
unitNomm, cm, m, inch or ft
angleNoBend angle in degrees (1-179)
lengthYesFlange length to the outer virtual sharp
radiusNoBend radius (default: the part's)
positionNoWhere the flange sits on the edgeinside

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does a solid job: it discloses that the call mutates the model, what it returns (volume added, flat size, relations added by SolidWorks rather than from the user's spec), and a failure condition (refused while flattened). It omits required permissions/part-state and error behavior beyond that single case.

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?

Three tight sentences, front-loaded with the operation and its geometric definition, then the enum semantics, then return values and the refusal condition. No filler; parenthetical glosses ('a wall bent up') earn their place for an unfamiliar CAD term.

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?

Six parameters all documented, no output schema yet the return payload is described, and the key blocking state is called out. The main remaining gap is the prerequisite that an active sheet-metal part must be open, which an agent would need before invoking.

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 exceeds it by defining each 'position' enum value (inside = outer face on edge, outside = inner face on edge, bend_outside = bend outside the edge) and by clarifying that 'length' is measured to the outer virtual sharp. It adds nothing for edge, unit, angle or radius, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Add an edge flange (a wall bent up) on the sheet metal edge through a point,' and pins the length convention to the outer virtual sharp. It implicitly separates itself from base/miter flanges by naming the edge-flange operation, but never names a sibling explicitly.

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 is implied through the geometry and the 'position' options, and one precondition is given ('Refused while flattened'). However, it never says when to choose this over miter_flange or sheet_metal_base_flange, nor what document state (active sheet-metal part) is required.

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