Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Check collisions

asm_check_collisions
Idempotent

Detect interference between assembly components and report each intersecting pair with its volume in mm3, using a temporary check that does not alter the assembly tree or create an Undo entry.

Instructions

Interference check between components of an assembly (all top-level components by default). Reports each intersecting pair and its volume (mm3). Temporary check object: no Undo entry, no tree change.

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": {
      "doc": "<doc>"
    },
    "name": "asm_check_collisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesAssembly document handle
componentsNoobj: handles; default all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond annotations: the check object is temporary, leaves no Undo entry, and does not modify the tree, which explains why readOnlyHint is false despite the harmless outcome. It does not say how long the temporary object lives or how to discard it, keeping it from 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 short sentences, front-loaded with the operation and scope, then the return content, then side effects. Every sentence carries distinct information with no filler.

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 simple two-parameter read-style tool, the definition covers purpose, default scope, returned data, and side-effect behavior. With no output schema present, the return description (intersecting pairs and their volumes) fills that gap adequately.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a nuance the schema lacks: the default scope is top-level components, implying nested components are excluded unless named. It still says nothing about handle format or ordering of the components list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific operation (interference check between assembly components) and the exact output (each intersecting pair plus volume in mm3), so the agent knows precisely what it gets back. It does not distinguish itself from the similarly-scoped inspect_check sibling, so it stops short of a 5.

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 only implied: the default scope ('all top-level components by default') tells the agent it can omit components for a whole-assembly check. There is no explicit when-to-use vs. when-not guidance and no mention of the inspect_check alternative.

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