Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Configurations

list_configurations
Read-onlyIdempotent

List an open part or assembly's configuration names and identify the active configuration before activating or deleting one; read-only.

Instructions

List the names of the active model's configurations, and which one is active.

Use it to see which configurations a part or assembly has before activate_configuration or delete_configuration. Needs: an open part or assembly. Read-only. Returns: configurations (names), count and active (null when it can't be read).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_configurations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so safety is covered; the description adds non-obvious context: a part or assembly must be open, and `active` may come back null when it can't be read. That null-edge-case disclosure is the kind of behavior an agent cannot get from annotations or schema.

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?

Front-loaded purpose sentence, then a usage clause naming siblings, then a compact prerequisite and returns line. Every sentence carries information and nothing is padded.

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?

The description gives the prerequisite (open document), the sibling routing, and the return shape, so even without opening the output schema an agent knows what it gets back. Nothing needed to invoke this zero-parameter read correctly is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies and there is nothing further for the description to disambiguate.

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 ('List the names of the active model's configurations') plus the extra scope detail of which one is active, which no sibling name reveals on its own.

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?

Explicitly places the tool in a sequence before `activate_configuration` and `delete_configuration`, so the agent knows which alternatives it feeds into. It stops short of stating when not to call it or what to do if no document is open.

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