Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Auxiliary plane / axis / point

aux_plane

Creates auxiliary planes, axes, and points at any angle for sketches, holes, and patterns, with offset, angle, three-point, and axis methods and undoable results.

Instructions

Auxiliary geometry for sketches, holes and patterns at any angle. kind=offset: plane parallel to base at offset mm; angle: plane through line (axis/edge) at angle° to base; three_points: plane through points; axis: by two_points | edge | two_planes | face (axis of a cylinder/cone face); point: at [x, y, z]. Points are [x, y, z] mm (an auxiliary point is made for each) or handles of vertices/points. The first created handle is the plane/axis/point. 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>"
    },
    "name": "aux_plane"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNopoint: [x, y, z] mm
byNoaxis: how it is defined
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
baseNooffset/angle: XY|ZX|ZY | obj: | topo: faceXY
kindNooffset
lineNoangle: X|Y|Z | obj: axis | topo: straight edge
nameNoMeaningful feature name for the tree, e.g. 'Отв_крепёжные_6xD11'
refsNoaxis edge/face: [topo:]; two_planes: two of XY|ZX|ZY|obj:|topo:
angleNoangle: degrees
offsetNooffset: mm
pointsNothree_points (3) / axis two_points (2): [x, y, z] mm or handles
reverseNooffset/angle: the other side

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.6.0
    • addedInput schema / properties / angle
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMaximum": 360,
      +      "exclusiveMinimum": -360,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "angle: degrees",
      +  "title": "Angle"
      +}
    • addedInput schema / properties / at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "number"
      +      },
      +      "maxItems": 3,
      +      "minItems": 3,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "point: [x, y, z] mm",
      +  "title": "At"
      +}
    • changedInput schema / properties / base / description
      Previous value: -"XY|ZX|ZY | obj: | topo: face"New value: +"offset/angle: XY|ZX|ZY | obj: | topo: face"
    • addedInput schema / properties / by
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "two_points",
      +        "edge",
      +        "two_planes",
      +        "face"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "axis: how it is defined",
      +  "title": "By"
      +}
    • addedInput schema / properties / kind
      Added value: +{
      +  "default": "offset",
      +  "enum": [
      +    "offset",
      +    "angle",
      +    "three_points",
      +    "axis",
      +    "point"
      +  ],
      +  "title": "Kind",
      +  "type": "string"
      +}
    • addedInput schema / properties / line
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "angle: X|Y|Z | obj: axis | topo: straight edge",
      +  "title": "Line"
      +}
    • changedInput schema / properties / offset / description
      Previous value: -"mm"New value: +"offset: mm"
    • addedInput schema / properties / points
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {},
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "three_points (3) / axis two_points (2): [x, y, z] mm or handles",
      +  "title": "Points"
      +}
    • addedInput schema / properties / refs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "axis edge/face: [topo:]; two_planes: two of XY|ZX|ZY|obj:|topo:",
      +  "title": "Refs"
      +}
    • addedInput schema / properties / reverse / description
      Added value: +"offset/angle: the other side"
  2. First observedv0.4.2

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it discloses transaction semantics ('the whole call is ONE Ctrl+Z'), rollback behavior on failure, the VERIFY_FAILED signal, and that the return is a receipt containing created handles, before/after volume-mass and a backup path. These are exactly the traits an agent cannot infer from readOnlyHint=false, destructiveHint=false, idempotentHint=false.

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?

It is front-loaded with purpose, then kind-to-parameter mapping, then return and failure behavior, with no filler sentences. The kind mapping is packed into semicolon-delimited fragments, which is efficient but dense enough that a reader can miss the shift from 'the first created handle' to the receipt.

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 12 parameters and no output schema, the description carries the return contract itself and does so (handles, before/after mass, backup path, VERIFY_FAILED). The remaining gap is modest: it doesn't say whether failures other than verification exist or how handles are formatted for downstream calls.

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 92%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: which parameters pair with which kind, that points may be raw [x,y,z] or handles of vertices, that an auxiliary point is auto-created per coordinate, and that the first created handle is the result. That is real meaning beyond the per-field descriptions.

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?

The first sentence states a concrete resource and scope: 'Auxiliary geometry for sketches, holes and patterns at any angle', and the following clauses enumerate the five construction kinds (offset, angle, three_points, axis, point). It is clear what the tool builds, but it never names a sibling or states how it differs from the pattern/hole features that also create reference geometry.

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?

Each kind is paired with its operative parameters (offset=..., angle=..., two_planes=..., face=...), which effectively tells the agent which combination to use for each construction. What is missing is any exclusion or prerequisite guidance, e.g. when to prefer a face-axis over two planes, or that refs must be resolved before calling.

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