Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

miter_flange

Creates a corner-mitred sheet-metal flange by sweeping an open profile sketch along edge chains, with rip gap and bend radius control.

Instructions

Add a miter flange: an open profile sketch (lines and arcs on a plane across a sheet edge, starting at that edge) swept along a chain of edges, mitred at the corners. edges: a point on each edge of the chain (default: the one edge the profile starts on). Returns the feature and the volume added. 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>"
    },
    "name": "miter_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapNoRip gap at corners (default 0.1 mm)
unitNomm, cm, m, inch or ft
edgesNoA point on each edge of the chain, the profile's edge first (default: that edge alone)
radiusNoBend radius (default: the part's)
sketchYesName of the open profile sketch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 it does disclose the return value (the feature and the volume added) plus a genuine state precondition (refused while flattened). It stops short of saying whether the source sketch is consumed/hidden, what units the volume is in, or what error surfaces on a bad edge chain.

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?

One dense but well-ordered block: what it builds, then the edges parameter note, then the return value, then the blocking condition. Front-loaded and free of filler.

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 no output schema, the explicit mention of the returned feature and volume fills the gap, and the sketch geometry requirement is stated for an otherwise complex modeling operation. Minor omissions are the sketch's post-call state and error behavior.

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 gap, unit, radius, edges, and sketch including the ordering default. The description reinforces edges ordering and the sketch's geometric requirements (open profile, lines and arcs, starting at a sheet edge), which adds interpretive value but no new syntax.

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?

Opens with a specific verb+resource ("Add a miter flange") and then defines the operation geometrically: an open profile sketch swept along a chain of edges and mitred at corners. That chain-of-edges/mitred-corner framing implicitly separates it from a single-edge flange, though no sibling is named.

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?

The description implies the applicable case (a chain of edges with corners to miter, profile starting on a sheet edge) but never states when to choose this over edge_flange or sheet_metal_base_flange. The one hard constraint given, "Refused while flattened", is the only explicit usage rule.

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