Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Hole

part_hole

Creates a hole feature on a planar face in KOMPAS-3D, optionally threaded, with through/blind depth and point or reference-distance positioning.

Instructions

Hole feature on a planar face (appears as «Отверстие» in the tree), optionally with a cosmetic thread from KOMPAS's own thread database (ГОСТ 24705-2004 by default: 'M8' = coarse pitch, 'M20x1.5' = fine). Position: at=[x, y] — a point on the face (on faces parallel to XY these are the global X, Y; required for round faces, which take no references) — or distances dist1/dist2 from two references ref1/ref2. With a thread and no diameter the hole diameter is the thread's minor diameter D1 from that database (M8 -> 6.647); pass diameter to use a tap drill instead (e.g. 6.8 for M8). Verified: the volume must shrink; receipt.removed_centroid_mm shows where the hole axis landed. For several identical holes use part_pattern on the result. Returns a receipt: created object handles, volume/mass before and after, backup path. The whole call is ONE Ctrl+Z for the user; if verification fails the model is restored and VERIFY_FAILED is returned.

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>",
      "face": "<face>"
    },
    "name": "part_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo[x, y] point on the face (global X, Y on faces parallel to XY)
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
endNoblind hole bottom: 118° drill point or flatcone
faceYestopo: planar face the hole starts on (select ... extreme)
nameNoMeaningful feature name for the tree, e.g. 'Отв_крепёжные_6xD11'
ref1Nofirst position reference: topo: side face / straight edge of a straight-edged face, or a default plane XY|ZX|ZY (from ZY the distance goes to +X, from ZX to -Y)
ref2Nosecond position reference, not parallel to ref1
depthNomm (blind hole)
dist1Nomm from ref1 to the hole axis
dist2Nomm from ref2 to the hole axis
threadNoe.g. 'M8', 'M20x1.5'
throughNothrough all
diameterNomm; optional when thread is given
standardNothread.db table, default 'cil1_24705-2004'
thread_lengthNomm; default = whole hole

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses verification behavior, volume-shrink check, receipt contents including removed centroid, backup path, rollback on failure, and that the whole call is one Ctrl+Z. This is unusually rich behavioral context for a mutation tool.

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?

The description is dense but front-loaded and every sentence provides useful information about a complex 15-parameter tool. It is a single long paragraph, but not padded or repetitive.

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 complex feature-creation tool with no output schema, the description covers purpose, positioning, threading, diameter behavior, verification, failure handling, undo semantics, receipt contents, and a pattern alternative. Nothing essential appears missing.

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. The description adds meaningful semantics for key parameters: at as a point on the face, ref1/ref2 distance positioning, thread string format, default minor diameter when thread is given, and tap-drill override via diameter.

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?

The description states a specific verb/resource: creating a hole feature on a planar face, optionally with a cosmetic thread, and notes the tree label. It also differentiates usage from part_pattern for several identical holes.

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?

It clearly explains positioning modes, thread/diameter behavior, and recommends part_pattern for several identical holes. It does not explicitly state when not to use this tool versus alternatives such as extrude or revolve.

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