Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

check_interference

Run an interference check on the active SOLIDWORKS assembly to get the count and each overlapping component pair with volume; optionally include touching faces.

Instructions

Run SolidWorks' interference check on the whole active assembly (parts inside sub-assemblies are checked one by one). Returns the number of interferences and, for each, the two components and the overlapping volume. Faces that merely touch are not counted unless treat_coincident_as_interference is true. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for the volumes, cubed (mm, cm, m, inch or ft)
treat_coincident_as_interferenceNoAlso count faces that merely touch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it declares the operation read-only, defines the boundary condition for what counts as an interference (touching faces excluded by default), and describes the return payload. It omits cost/performance on large assemblies and failure behavior, which keeps it short of a 5.

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?

Three tight sentences: scope first, return shape second, counting rule third, safety flag last. No filler and no repetition of the tool name.

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?

For a two-optional-parameter tool with no output schema, the description supplies everything needed: what is scanned, how results are structured, and the one semantic edge case. Nothing an agent requires to invoke it correctly is missing.

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%, so both parameters are already documented in the schema, and the description's note on treat_coincident_as_interference largely restates the schema default. The unit parameter is not elaborated at all, so no meaning is added beyond structured fields.

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 (run interference check) and resource (the whole active assembly), and pins down scope with 'parts inside sub-assemblies are checked one by one.' An agent immediately knows this is a whole-assembly clash detection tool, distinct from dimension, mate, or component tools in the sibling list.

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?

Usage is implied rather than stated: the tool only ever checks the entire active assembly, so the agent can infer it must be in an assembly document, and the coincident-face note hints at the main decision point. However, it never says when to reach for this versus other validation tools or what to do if no assembly is active.

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