Skip to main content
Glama

Check for collisions

check_interference
Read-onlyIdempotent

Find which parts physically overlap, and by how much volume. This is the assembly check you cannot do by reasoning about a tree OR by looking at a render — an interference is usually hidden inside the model. Run it on anything with more than one part that is meant to fit together.

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
scadNoOpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses; BOSL2/MCAD includes resolve. minkowski() and resize() are not supported here — use hull() or offset().
nodesNoParametric node tree. mm, Z-up, rotations in DEGREES (a rotation.* binding: radians). Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong.
projectIdNoId of one of your saved projects, as an alternative to `nodes`/`scad` (supply exactly one).
smoothnessNoCurve quality for shapes that left their segment count automatic. Defaults to "standard", which is the editor default — pass "high" to match a project authored at high smoothness, "draft" for a cheaper check.
minVolumeMm3NoIgnore overlaps smaller than this (default 0.001). Parts that merely share a face graze each other numerically; this is what stops that being reported as a collision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / generatorKey / description
      Previous value: -"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."New value: +"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · bevelPair · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."
  2. Changed1 schema field changed
    • changedInput schema / properties / nodes / description
      Previous value: -"Parametric node tree. mm, Z-up, rotations in DEGREES. Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong."New value: +"Parametric node tree. mm, Z-up, rotations in DEGREES (a rotation.* binding: radians). Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong."
  3. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / generatorKey / description
      Previous value: -"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap."New value: +"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."
  4. Changed1 schema field changed
    • changedInput schema / properties / scad / description
      Previous value: -"OpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses. minkowski() and resize() are not supported here — use hull() or offset()."New value: +"OpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses; BOSL2/MCAD includes resolve. minkowski() and resize() are not supported here — use hull() or offset()."
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds useful conceptual context — interference is typically hidden inside the model, so a geometric check is required — but says nothing about cost, runtime, or how results are reported for large assemblies.

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?

Front-loaded with the outcome and volume measure in the first sentence, then the disambiguation, then the trigger condition — a sensible order with no wasted preamble. The em-dash aside about renders is slightly rhetorical but still earns its place as disambiguation.

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?

Five optional parameters and no output schema mean the description should ideally signal what a result contains (which part pairs, volume per overlap), and it only promises 'by how much volume' in passing. Everything needed to decide when and how to invoke it is present, so the gap is in return-shape expectation rather than invocation.

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 description coverage is 100%, and the schema itself documents the scad/nodes/projectId alternatives, smoothness levels, and the minVolumeMm3 grazing-tolerance rationale in detail. The description contributes no additional parameter meaning beyond that, which is the expected baseline when the schema carries the full burden.

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 and outcome — 'find which parts physically overlap, and by how much volume' — which tells an agent exactly what the tool returns and how it differs from render or measure. The added framing that this is an assembly check that cannot be done by inspecting a tree or a render further separates it from the sibling tools.

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?

'Run it on anything with more than one part that is meant to fit together' gives a concrete applicability condition, and the explicit exclusion of tree reasoning and render inspection steers the agent away from substitutes. It stops short of naming sibling tools like measure or print_check as alternatives, so routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources