Skip to main content
Glama
solidworks-mcp

solidworks-mcp

edge_flange

Bends a sheet-metal flange along a straight edge to a specified length, with optional angle and bend radius; use a selected edge or an edge point from a base flange.

Instructions

Bends a flange of length_mm along a straight edge of a sheet metal part (made with base_flange): edge_point_mm is a point [x, y, z] in mm on that edge, or the edge selected with select_edge_at_point is used. The flange is as wide as the edge; radius_mm = 0 uses the bend radius of the part. Replaces the current selection.

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": {
      "length_mm": "<length_mm>"
    },
    "name": "edge_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
angle_degNoFlange bend angle in degrees (default 90)
length_mmYesFlange length in mm
radius_mmNoBend radius in mm; 0 uses part default
edge_point_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already disclose the non-read-only, non-idempotent, non-destructive profile, so the description's main contribution is the side effect 'Replaces the current selection' and the default-resolution rule 'radius_mm = 0 uses the bend radius of the part.' These are genuine state-changing details not present in annotations; error behavior and reversibility remain unstated.

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?

Front-loaded with the action, then parameters, then side effects; every clause carries information (dependency, edge format, width behavior, radius default, selection replacement). It is dense and slightly run-on, mixing several facts into long sentences, but no sentence is 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?

For a four-parameter sheet metal modeling tool with an output schema, this covers prerequisites, geometry defaults, edge referencing, and the selection side effect. What is missing is failure guidance (e.g., a point not on an edge) and whether the original flange can be recovered, but the essentials for correct invocation are present.

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 75%, and the one gap is edge_point_mm, which has no schema description; the description compensates by defining it as an [x, y, z] point in mm on the edge and explaining the fallback to the selected edge. It restates the radius_mm default already in the schema, but the edge-point clarification adds real meaning.

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: 'Bends a flange of length_mm along a straight edge of a sheet metal part.' It also anchors the tool to its sibling by noting the part is 'made with base_flange' and that the edge can come from select_edge_at_point, so an agent can separate this from the base-geometry and edge-selection tools without opening schemas.

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?

Gives clear operating context: the part must be a sheet metal part created with base_flange, and the bend edge comes either from edge_point_mm or from a prior select_edge_at_point selection. It does not spell out explicit when-not conditions or what happens on an invalid edge, but the prerequisite chain is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.