Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

structural_member

Create weldment structural members along sketch lines and arcs from installed profile libraries, choosing standard, type, size and corner treatment. Returns the feature, bodies and lengths.

Instructions

Make weldment structural members along the lines and arcs of a sketch, from the installed profile library: standard (e.g. iso, ansi, DIN), type (e.g. square tube) and size (e.g. 20 x 20 x 2). corner decides how members meet: miter, butt1, butt2 or none; butt1 / butt2 give SolidWorks' pinwheel: each member runs through at one end and stops at the other, so every member is exactly as long as its path (the butt joint as built, nothing to trim). An unknown standard, type or size is refused with the list of choices. Returns the feature, the bodies and their lengths.

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>",
      "type": "<type>",
      "size": "<size>",
      "standard": "<standard>"
    },
    "name": "structural_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesProfile size, e.g. 20 x 20 x 2
typeYesProfile type, e.g. square tube
cornerNoCorner treatmentmiter
sketchYesName of the sketch whose segments are the member paths
standardYesProfile standard folder, e.g. iso

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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; it discloses the invalid-input behavior ('refused with the list of choices'), the geometric consequence of butt1/butt2 ('each member runs through at one end and stops at the other, so every member is exactly as long as its path'), and the return contents. It omits document-state prerequisites (an open part, an existing sketch) and whether the operation is re-runnable or undoable, which matters for a creation tool with zero annotation coverage.

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?

Dense and front-loaded: the action, the profile coordinates, the corner semantics and the return value appear in that order with no filler. Minor redundancy comes from re-listing the example values already present in the schema.

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 a five-parameter creation tool with no annotations and no output schema, the description supplies the geometry semantics, the failure mode, and an explicit statement of what is returned (feature, bodies, lengths). The only gap is document-state prerequisites, which is minor relative to what is covered.

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 all five parameters are already documented; the description's standard/type/size examples ('iso', 'square tube', '20 x 20 x 2') merely repeat the schema descriptions. It does add genuine meaning for 'corner' beyond the schema's bare 'Corner treatment', explaining the pinwheel semantics of butt1/butt2 and that nothing needs trimming, which lifts it above the baseline.

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: 'Make weldment structural members along the lines and arcs of a sketch'. It names the source geometry (sketch segments) and the profile library dimensions (standard/type/size), which distinguishes it from sketch-creation siblings like create_sketch.

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?

Presents the prerequisites for use implicitly (a sketch whose lines/arcs are the paths, an installed profile library) and explains the corner-choice decision across all four enum values. It does not name an alternative tool or state when not to use it, so it stops short of a full routing guide.

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