Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Check geometry / measure

inspect_check
Idempotent

Check KOMPAS part geometry for open edges, self-intersections, tiny objects or spikes, or measure min/max distance, closest points and angle between two objects.

Instructions

KOMPAS geometry check of a part (open edges, self-intersections, tiny objects, spikes...), or with measure the distance between two objects: min/max distance (mm), the closest points, the angle and their relation (surfaces_parallel, axes_coaxial, …; normal_distance_mm for parallel ones) — e.g. a wall thickness, the gap between assembly components, whether a hole is coaxial. Temporary objects only: no Undo entry, no tree change, the «changed» flag is kept. Collisions: asm_check_collisions.

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

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
checksNodefault: all
measureNo[obj1, obj2] — measure instead of checking: topo: faces/edges from select, obj: features, planes, axes or assembly components, XY|ZX|ZY
linear_tolerance_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / measure
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 2,
      +      "minItems": 2,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "[obj1, obj2] — measure instead of checking: topo: faces/edges from select, obj: features, planes, axes or assembly components, XY|ZX|ZY",
      +  "title": "Measure"
      +}
  2. First observedv0.4.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world behavior, yet the description adds genuinely new context: results are temporary objects, no Undo entry is created, the feature tree is untouched, and the 'changed' flag is preserved. That explains why readOnlyHint is false despite no persistent modification. It does not cover cost, tolerance effects, or failure modes.

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?

One dense paragraph that front-loads the checking mode, then the measure mode, then the behavioral caveat and the sibling redirect — a logical order with no filler. The parentheticals and em dashes pack detail without wasted sentences.

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 does the work of describing measure returns (min/max distance in mm, closest points, angle, relations such as surfaces_parallel and axes_coaxial, normal_distance_mm). For the check mode the shape of the result is left implicit. Given four parameters and a two-mode tool, this is close to complete but not fully.

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 75%, so the schema already carries most parameter meaning, including the [obj1, obj2] measure pair and the accepted object types. The description's list of defect kinds loosely echoes the `checks` enum and the measurement examples hint at `measure`, but it never explains `linear_tolerance_mm` or how the two modes interact. Baseline 3 is appropriate.

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 the specific verb and resource ('KOMPAS geometry check of a part') and enumerates the check kinds (open edges, self-intersections, tiny objects, spikes), then names the second mode explicitly ('or with `measure` the distance between two objects'). An agent can distinguish this from inspect_model or asm_check_collisions without opening any schema.

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?

Gives concrete use cases for the measure mode (wall thickness, gap between assembly components, hole coaxiality) and explicitly routes collisions elsewhere ('Collisions: asm_check_collisions'). It also clarifies the mode switch ('measure instead of checking'). It stops short of full when-not-to-use guidance, e.g. when to prefer inspect_model or which check set to choose for a given defect class.

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