Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_component_fixed

Fix a top-level component in the active assembly to prevent mates and move operations from moving it, or release it to float again.

Instructions

Fix a top-level component of the active assembly where it is, or release it (fixed = false). Mates and move_component cannot move a fixed component. The state read back is reported; list_components shows it as 'fixed'.

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_component_fixed"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedNotrue = fix, false = float
componentYesComponent name from list_components

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?

With no annotations, the description carries the burden and does reasonably well: it discloses the effect on mates and move_component, that the resulting state is read back, and how list_components will report it. It omits persistence scope (assembly-level vs document) and any permission requirements, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary action, then the constraint, then the verification path. No redundant or filler wording.

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 two-parameter mutation tool with no output schema and no annotations, the description covers the action, the inverse, the side effects on other tools, and how to verify the result. Only permission/persistence details are missing.

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 the schema already documents both parameters, including 'true = fix, false = float'. The description reinforces the release semantics of fixed = false but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 (fix/release) on a specific resource (top-level component of the active assembly) and clarifies the inverse operation via fixed = false. An agent can distinguish it from move_component and set_component_visibility without opening the 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?

Explains the consequence of fixing ('Mates and move_component cannot move a fixed component'), which tells the agent when fixing is appropriate and what it blocks. It stops short of explicitly naming when to prefer release over fix, but the context 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