Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

move_component

Move a floating component to a specified origin position and orientation in a SOLIDWORKS assembly, using absolute or relative coordinates and rotations.

Instructions

Move a floating top-level component to a position and orientation in the assembly. x, y, z are where its ORIGIN goes, in assembly coordinates (an omitted one stays). Orientation: rx, ry, rz in degrees applied about the assembly X, then Y, then Z axis starting from axes parallel to the assembly's, or one turn of angle degrees about axis. With relative = true, both are a shift from the current pose, about the component's own origin. Mates still apply: the result says where the component ended up and whether that is where it was put. A fixed component is refused.

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": {
      "component": "<component>"
    },
    "name": "move_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX of the component's origin (or the shift along X with relative)
yNoY of the component's origin (or the shift along Y)
zNoZ of the component's origin (or the shift along Z)
rxNoDegrees about the assembly X axis
ryNoDegrees about the assembly Y axis (applied after rx)
rzNoDegrees about the assembly Z axis (applied last)
axisNoInstead of rx / ry / rz: the direction to turn about
unitNoUnit of x, y, z (mm, cm, m, inch or ft)
angleNoWith axis: degrees to turn
relativeNotrue = shift and turn from where it is now
componentYesComponent name from list_components

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 so well: it discloses the non-obvious side effect that mates still constrain the result and that the response reports actual versus requested pose, plus the refusal behavior for fixed components. It omits permission requirements, persistence/undo semantics, and any failure modes beyond the fixed-component case.

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 and target, then quickly covers coordinates, orientation order, relative mode, and mate behavior in dense but purposeful sentences. No filler, though the single packed paragraph makes it slightly harder to scan the three distinct modes (absolute, axis/angle, relative).

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 an 11-parameter mutation tool with no annotations and no output schema, the description covers the critical unknowns: coordinate frame, rotation composition order, relative semantics, mate interaction, and what the result reports. The 'unit' parameter and any undo/rollback behavior are left undocumented, which keeps it just under fully complete.

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% and already documents every parameter, including rotation order and the relative flag, so the baseline is 3. The description adds genuine meaning on top — assembly coordinates, 'an omitted one stays', the starting axis reference frame, and that relative shifts are about the component's own origin — but much of that overlaps the schema's existing per-parameter text.

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 ('Move a floating top-level component') plus the scope of the operation (position and orientation in the assembly). The qualifier 'floating top-level' immediately distinguishes it from fixed-component or sub-component operations and from sibling tools like replace_component or move_drawing_view.

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?

The description supplies real preconditions: the component must be floating, a fixed component is refused, and mates still apply. It stops short of naming alternatives or stating when to prefer this over, say, re-mating or replacing a component, but the applicability boundary is clear.

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