Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Delete Configuration

delete_configuration
Destructive

Removes a non-active, non-only configuration from the open SolidWorks part or assembly; activate another configuration first to delete the active one.

Instructions

Delete a configuration of the active model; not the active one or the only one.

Activate another configuration first to delete the active one. Needs: an open part or assembly with that configuration. Changes: removes it. Returns: deleted and the configurations left.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`name`, the configuration to delete.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false and idempotent=false; the description adds what actually disappears, the guarding constraints, and the shape of the result. It does not say what happens if the named configuration does not exist (error vs. no-op), which matters given idempotentHint=false.

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 with the constraint that determines success, then a terse Needs/Changes/Returns structure. No filler sentences; every clause carries a fact the agent needs (exclusion rules, prerequisite, effect, result).

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 destructive one-parameter tool it covers the prerequisite state, the deletion guard, and the effect. The Returns line is largely redundant since an output schema exists, and failure behavior for a missing configuration name is left implicit.

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 single nested `name` parameter already carries a description and an example. The description only restates that the name identifies a configuration of the active model; with the schema doing the heavy lifting, baseline 3 is appropriate.

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?

Specific verb+resource ("Delete a configuration of the active model") plus immediate scope exclusions ("not the active one or the only one") that separate this from activate_configuration/create_configuration work. An agent can tell exactly what this tool does 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not conditions (cannot delete the active or the only configuration), and a concrete workaround for the blocked case ("Activate another configuration first"). The prerequisite "an open part or assembly with that configuration" gives the state that must hold before calling.

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