Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_subassembly_solving

Set a sub-assembly as rigid or flexible in the active assembly so its parts either move as one piece or move within their own mates when dragged or mated.

Instructions

Make a sub-assembly component rigid or flexible in the active assembly. Rigid (SolidWorks' default) moves as one piece; flexible lets the sub-assembly's own parts move, within its own mates, when they are mated or dragged in this assembly. The state read back is reported; list_components shows it as 'solving'.

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": "set_subassembly_solving"
  }
}

Input Schema

NameRequiredDescriptionDefault
solvingNoflexible or rigidflexible
componentYesName of the sub-assembly component from list_components, e.g. 'Chain-1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 disclose real behavior: SolidWorks' default is rigid, flexible applies within the sub-assembly's own mates, and the resulting state is reported back. It omits prerequisites (an active assembly, component actually being a sub-assembly), what happens on invalid targets, and whether the change is undoable.

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?

Three sentences, front-loaded with the action, then the mode semantics, then the reporting note; nothing is padded. Only the final sentence ('The state read back is reported') is slightly awkward in phrasing.

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 simple two-parameter tool this covers the essentials: what it does, what each mode means, and that the state is observable afterward, with no output schema needed. Missing are prerequisite conditions (active assembly, sub-assembly vs part) and failure behavior, which matter for a mutation tool with no annotations.

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 100%, so the baseline is 3; the description earns above that by giving the otherwise uninformative 'flexible or rigid' enum real semantics — one moves as a single piece, the other lets internal parts move within their own mates. It also reinforces that the component name comes from list_components.

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?

States a specific verb+resource ('Make a sub-assembly component rigid or flexible') and scopes it to 'the active assembly', so the agent knows exactly what changes. It does not explicitly distinguish itself from the nearby sibling set_component_fixed, which an agent could plausibly confuse with the 'rigid' state.

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?

Usage is implied rather than stated: the description explains the effect of each mode and points to list_components for reading the state back, which helps an agent verify results. It never says when to choose this versus set_component_fixed or what prerequisites must hold, leaving the when-to-use decision to inference.

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