Skip to main content
Glama

Interference Check

interference_check
Read-only

Detect clashes between every pair of parts by computing intersection volumes, returning pairs sorted by severity; an empty list confirms no interference.

Instructions

Pairwise interference: compute volume of intersection between every pair of parts. Returns [{a, b, interference_mm3}, ...] descending by volume. Empty list = no interference.

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": {
      "assembly": "<assembly>"
    },
    "name": "interference_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
assemblyYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral value by disclosing the return shape ([{a, b, interference_mm3}, ...]), ordering (descending by volume), and the empty-list semantics. It omits that pairwise checks scale O(n²) and could be slow on large assemblies, which is a meaningful gap but not fatal.

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 short sentences, front-loaded with what is computed, followed by return shape and the empty-list interpretation. No 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?

With no output schema, the description adequately explains return values, and annotations cover safety. Minor gaps remain around the 'assembly' parameter format and computational cost, but an agent can call it correctly from what is provided.

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 only 50%: the 'assembly' parameter has no description while 'workspace' does. The description implies assembly is a container of parts but does not specify its expected form (name, path, handle), leaving the undocumented parameter under-explained. Baseline 3 fits since the schema covers part of the 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 resource: 'compute volume of intersection between every pair of parts' with pairwise scope. It is clearly distinguishable from siblings like min_clearance, envelope_check, and boolean_op, which do not compute pairwise part intersections.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as min_clearance or envelope_check, and no prerequisites (e.g. parts must be in an assembly, units assumed in mm). The only interpretive note, 'empty list = no interference', explains output, not when to invoke it.

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