solidworks-mcp

Overview Schema Source Related Servers Discussions Admin

solidworks_configuration

Destructive

Manage SOLIDWORKS configurations by adding, listing, deleting, activating, and modifying design tables or dimension values.

Instructions

solidworks_configuration: dispatches on payload.operation to one of the capability-module handlers for [activate, add, delete, delete_design_table, get_design_table, insert_design_table, list, set_config_dimension]. Each operation has its own typed field set (see the tool's input schema); unspecified fields fall back to the module function's own default. Lengths/angles follow each field's documented unit convention (SI unless the function accepts a unit field).

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": {
      "payload": "<payload>"
    },
    "name": "solidworks_configuration"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	Yes
`document`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior2/5

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

The description only mentions dispatch mechanics and does not disclose potential side effects (e.g., deletion, modification, activation) that some operations perform. While the annotations indicate destructive behavior, the description itself adds no transparency about the impact of individual operations.

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?

The description is very concise, using only a few sentences to convey the dispatcher pattern and the list of operations. No unnecessary words or repetition, making it easy to read and understand.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the dispatch mechanism and fallback behavior, but does not mention what the tool returns or how the output might vary by operation. Given that an output schema exists, a brief note on return shape would improve completeness, but it is not critical for basic usage.

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 schema already provides detailed parameter definitions, defaults, and required fields. The description adds value by clarifying the unit convention for length/angle fields, which is not evident from the schema alone. This helps interpret the 'unit' parameter correctly.

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?

The description clearly states that the tool dispatches on payload.operation to specific handlers for configuration operations, and lists all supported operations. This makes the purpose unambiguous and distinct from sibling tools focused on other SolidWorks aspects.

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?

It explains that each operation has its own typed field set and that unspecified fields fall back to defaults, guiding usage. It does not explicitly state when to prefer this tool over siblings, but the operation list and name make it evident for configuration tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server