Skip to main content
Glama
Sign In
solidworks-mcp

solidworks-mcp

by rdolan5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

solidworks_script

Destructive

Run Python scripts to automate SOLIDWORKS CAD/CAM operations, including assemblies, equations, and lengthy computations in background jobs.

Instructions

Execute trusted Python on the COM apartment (--allow-scripts required). Globals: sw, cad, cam, gateway, call(obj,member,*args), workspace, parameters. Assign result. Supports loops, equations, advanced features, assemblies and arbitrary add-ins. Full local code execution, not a sandbox. Prints are captured. Background jobs allow lengthy CAD/CAM computation.

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": {
      "source": "<source>"
    },
    "name": "solidworks_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
backgroundNo
parametersNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Adds significant context beyond annotations: 'not a sandbox' warns of full access, 'Prints are captured' describes output behavior, 'Globals: sw, cad, cam...' explains the environment, and 'Background jobs' explains concurrency. Aligns with destructiveHint and openWorldHint.

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?

The description is a single dense paragraph, front-loaded with the core action. Every sentence adds value: environment, capabilities, and notes on execution. Efficient and appropriately sized for a complex tool.

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?

Covers the script environment, supported features, background execution, and non-sandbox nature. With an output schema present, it doesn't need to detail return values. It could be more explicit on how to assign results, but overall adequate for a script execution tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must explain parameters. It mentions 'parameters' as a global but does not directly explain the 'source' or 'background' parameters. 'Background jobs' hints at the background parameter, but no explicit mapping. Fails to fully compensate for missing schema descriptions.

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?

Clearly states 'Execute trusted Python on the COM apartment', specifying the verb and resource. Also differentiates from siblings by noting it's 'Full local code execution, not a sandbox', implying generic script execution vs. specific operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Provides some guidance: 'Background jobs allow lengthy CAD/CAM computation' suggests when to use background. But does not explicitly mention alternatives or when not to use this tool. The generic nature is implied but not contrasted with siblings.

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