Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_component

Insert a saved part or sub-assembly into the active SOLIDWORKS assembly at specified X, Y, Z coordinates, with optional rotation about the assembly axes or a custom axis.

Instructions

Insert a saved part or sub-assembly file into the active assembly, with the centre of its bounding box at x, y, z. It can be rotated about that centre: rx, ry, rz in degrees (applied about the assembly X, then Y, then Z axis), or one turn given as axis plus angle. The first component inserted is fixed; later ones float until mated (add_mate). set_component_fixed changes that, and move_component repositions a floating one.

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": {
      "filepath": "<filepath>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "add_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX of where the component's center goes
yYesY of where the component's center goes
zYesZ of where the component's center goes
rxNoTurn it by this many degrees about the assembly X axis
ryNo... then about the assembly Y axis
rzNo... then about the assembly Z axis
axisNoInstead of rx / ry / rz: the direction to turn about
unitNomm, cm, m, inch or ft
angleNoWith axis: degrees to turn
filepathYesPath of the .SLDPRT / .SLDASM file

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 burden and does well: it discloses the rotation composition order (assembly X, then Y, then Z), the axis+angle alternative, and the important fixed-vs-floating lifecycle of inserted components. It omits error/permission behavior and, notably, how the created component is identified afterwards, which matters for chaining into add_mate.

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?

Placement and rotation come first, lifecycle and sibling routing last — good front-loading with no filler. The parentheticals ('(applied about the assembly X, then Y, then Z axis)', '(add_mate)') are dense but each carries information, so little is wasted.

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 10-parameter mutation tool with a nested axis object, no annotations, and no output schema, the description covers geometry and lifecycle well but leaves gaps: what identifier comes back for the new component, what unit applies to the coordinates, and what happens on a missing or duplicate file. These are the details an agent needs to chain the call into add_mate correctly.

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 baseline is 3. The description adds only marginal meaning beyond the schema — 'centre of its bounding box' is slightly more precise than the schema's 'center', and the rx/ry/rz ordering is already spelled out in the property descriptions. The 'unit' parameter is never mentioned in the description, leaving unclear which values it scales.

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 (insert) and resource (saved part/sub-assembly file) with an explicit target (the active assembly) and placement semantics. It also names the sibling tools it relates to (add_mate, set_component_fixed, move_component), so an agent can distinguish it from the rest of the catalog without opening another schema.

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?

Provides real usage context: the first component becomes fixed, subsequent ones float until mated, and set_component_fixed / move_component are named as the follow-up routes. It stops short of stating explicit exclusions (e.g., when to use replace_component instead of re-inserting), so it is clear but not fully routing.

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