Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Component State

set_component_state
Idempotent

Fix or float components in an open assembly, or make sub-assemblies rigid or flexible, so mates position parts correctly while preserving existing visibility, suppression, and configuration.

Instructions

Fix or float a component of the active assembly, or make a sub-assembly rigid or flexible.

Float a part so mates can position it (the first part inserted is fixed); fix one to hold it still. Make a sub-assembly flexible so its own mates move in this assembly (a crank whose knob turns). Only what you pass changes: the component's suppression, visibility and configuration are kept. Needs: an open assembly. Changes: the component's fixed or solving state. Returns: state with component, before and after (fixed, flexible and the properties kept).

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": {
      "input_data": "<input_data>"
    },
    "name": "set_component_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe component and what to change: `fixed`, `flexible` or both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing a partial-update guarantee: 'Only what you pass changes: the component's suppression, visibility and configuration are kept.' It also states the prerequisite and the exact shape of the returned state with before/after values.

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 core action, then cleanly labeled blocks for Needs / Changes / Returns. Slightly repetitive of the schema's own parameter wording (e.g. floating so mates move), which costs a point but does not obscure anything.

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 single-parameter mutation tool, the description covers what it mutates, what it preserves, the prerequisite, and the return payload. Even though an output schema exists, the explicit return summary makes the definition self-contained.

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 descriptions already explain fixed, flexible and component, so the description's restatement of those semantics adds little new meaning. The 'only what you pass changes' rule is helpful context but is behavioral rather than parameter-level detail.

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?

Opens with a specific verb set and resource: 'Fix or float a component of the active assembly, or make a sub-assembly rigid or flexible.' The three modes of operation are named explicitly, and the tool is clearly distinguishable from siblings like insert_component or add_mate.

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?

Gives concrete when-to-use rationale for each mode: float 'so mates can position it', fix 'to hold it still', flexible so 'its own mates move in this assembly (a crank whose knob turns)'. It also states the prerequisite ('Needs: an open assembly') and the nuance that the first inserted part is fixed. It stops short of naming alternatives or explicit when-not conditions.

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