Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Revolve

part_revolve

Create or cut a revolved feature from a sketch around an axis, returning object handles and verification with automatic backup and single-step undo.

Instructions

Boss or cut by revolution of a sketch about an axis (shafts: axis X, sketch on XY). 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>",
      "sketch": "<sketch>"
    },
    "name": "part_revolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoboss
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
axisNoX|Y|Z | obj: axis | topo: straight edgeX
nameNoMeaningful feature name for the tree, e.g. 'Отв_крепёжные_6xD11'
angleNodegrees
sketchYesobj: handle from inspect_model/receipt, or '$N' inside batch
new_bodyNoboss as a SEPARATE body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / new_body
      Added value: +{
      +  "default": false,
      +  "description": "boss as a SEPARATE body",
      +  "title": "New Body",
      +  "type": "boolean"
      +}
  2. First observedv0.4.2

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations it discloses genuinely non-obvious behavior: the call is atomic for the user (one Ctrl+Z), it takes a backup, verifies the result, and rolls the model back with VERIFY_FAILED on failure. It also enumerates the receipt payload (object handles, volume/mass before and after, backup path). What is missing is whether a 'cut' requires an existing body or what permissions/locks apply, but the transactional contract is well covered.

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?

Three tight sentences: operation first, then return payload, then the safety/rollback contract. Information density is high with no filler, though the parenthetical list of receipt fields and the Ctrl+Z remark are compressed into a way that slightly crowds the front-loading.

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 correctly takes on the burden of describing the return value and error mode, which it does. For a 7-parameter mutation tool it is nearly complete; only per-parameter behavior (notably new_body and cut-vs-boss prerequisites) is left entirely to the schema.

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 86%, so most parameters are already documented in the schema. The description only adds incidental meaning to 'axis' and 'sketch' via the shafts example and says nothing about op, angle, name, or new_body beyond restating the revolve concept, so the baseline 3 is appropriate.

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?

States a specific verb and resource: 'Boss or cut by revolution of a sketch about an axis', including the operation enum semantics and the axis/sketch-plane convention. It never names the adjacent modeling siblings (part_extrude, part_sweep_loft), so an agent must infer the boundary from the word 'revolution' alone.

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?

The parenthetical '(shafts: axis X, sketch on XY)' gives a concrete typical setup, which is useful implied guidance. There is no explicit statement of when to choose revolve over extrude/sweep_loft, and no exclusions or preconditions such as the sketch needing to be a closed profile or lying off the axis.

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