Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Configuration

create_configuration

Adds a named configuration to the active SolidWorks part or assembly, optionally derived from a parent, to manage variant dimensions and suppressed features.

Instructions

Add a configuration to the active part or assembly, e.g. a long and a short version of one part.

A configuration holds its own dimension values and suppressed features; give parent to derive it from another. The configuration that was active stays active unless activate is on. Needs: an open part or assembly. Changes: adds a configuration. Returns: configuration with name, parent, active and every name in configurations.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe configuration. `name` is required; `parent`, `description` and `activate` are optional.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description usefully adds that the previously active configuration stays active unless `activate` is set and that configurations carry their own dimension values and suppressions. It does not address the non-idempotent case the annotations imply (e.g. what happens on a duplicate name), leaving a meaningful gap for a mutation tool.

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 purpose and example, then structured Needs/Changes/Returns lines that are easy to scan; no filler sentences. The 'Returns:' line largely duplicates the output schema, which is the only wasted content.

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?

With an output schema and annotations present, the description supplies the missing pieces: the document prerequisite, the domain meaning of a configuration, and the side effect on the currently active configuration. Only edge-case behavior (duplicate names, failure modes) is unaddressed, which is minor at this complexity.

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 nested fields (name, parent, activate, description) are already documented in the schema, including the child-derivation meaning of `parent`. The description mostly restates the activate default rather than adding syntax or constraint detail, so the baseline of 3 applies.

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?

A specific verb and resource ('Add a configuration to the active part or assembly') plus a concrete example ('a long and a short version of one part'). The verb cleanly separates it from activate_configuration and delete_configuration, but the description never names those siblings explicitly.

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 a clear prerequisite ('Needs: an open part or assembly') and states the 'give `parent` to derive it from another' condition, which is real when-to-use guidance embedded in the text. It stops short of explicit when-not or comparison against activate_configuration/delete_configuration.

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