Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Check Assembly Interference

check_interference
Read-onlyIdempotent

Detect overlapping components in an active SolidWorks assembly. Returns interference count, component pairs, and overlap volume in mm³.

Instructions

Find where the components of the active assembly overlap (Tools > Interference Detection).

Use it after inserting and mating components. A count of 0 is a real measurement. To fail a build on interference, use verify_model with no_interference. Needs: an open, active assembly. Read-only. Returns: data with interference_found, interference_count, interferences (component pairs and overlap volume in mm³) and scope.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesNothing is required. `components` limits the report to interferences involving those components; `include_hidden` also checks hidden components, which are left out by default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description still adds the activation precondition and the important interpretive caveat that a count of 0 is a real measurement rather than an error. It does not cover cost/latency or behavior on large assemblies, so it is not exhaustive, but it adds genuine context beyond the annotations.

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?

It is short and front-loaded, with purpose first, then timing, then prerequisite, then return shape. The 'Returns:' clause partly duplicates the existing output schema, which is the only wasted text.

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 read-only check with a full input schema and an output schema, the definition covers purpose, timing, prerequisites and the escalation path to verify_model. The enumerated return fields are redundant given the output schema, slightly inflating length without adding information.

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%, including nested descriptions of components and include_hidden, so the schema carries parameter meaning on its own. The description adds no syntax or format detail for components (e.g. exact-name matching) and thus earns the baseline rather than more.

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 uses a specific verb and resource (find overlapping components in the active assembly) and anchors it to the SolidWorks UI path (Tools > Interference Detection). It also distinguishes itself from verify_model, so an agent can route between the diagnostic check and the gating check without opening either 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?

It states when to run it (after inserting and mating components) and names the explicit alternative for the gating case: verify_model with no_interference. The prerequisite of an open, active assembly is spelled out, leaving nothing to inference.

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