Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Sweep / loft

part_sweep_loft

Create swept or lofted features in KOMPAS-3D parts by moving a profile along a path or building a body through ordered section sketches, with boss/cut verification and single-step undo.

Instructions

kind=sweep (кинематическая операция): a closed profile sketch moved along a path — a path sketch and/or edges that START on the profile's plane (pipes, springs, bent rods). kind=loft (по сечениям): a body through 2+ closed section sketches in order, each on its own plane (aux_plane), e.g. a round-to-square transition. Verified like extrusions: boss must add volume, cut must remove it. 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>",
      "kind": "<kind>"
    },
    "name": "part_sweep_loft"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoboss
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
kindYes
nameNoMeaningful feature name for the tree, e.g. 'Отв_крепёжные_6xD11'
pathNosweep: path sketch (obj:/$N) and/or topo: edges, in order
shiftNosweep: how the profile follows the path; keep_angle (default) keeps its angle to the pathkeep_angle
closedNoloft: close the loft back to the first section
profileNosweep: obj: / $N of the profile sketch
sectionsNoloft: section sketches in order (obj:/$N)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.9/5.0
Behavior3/5

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

Goes well beyond the annotations by disclosing the verification gate (boss must add volume, cut must remove it), the failure path (model restored, VERIFY_FAILED), and that the whole call is one undo step. However, it does not say what happens when a cut removes more volume than intended or how the receipt behaves on partial success; combined with destructiveHint=false for an operation that removes material, this leaves some ambiguity.

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 dense but well organized: mode definitions first, constraints second, verification and return contract last. Bilingual glosses and some redundancy (e.g. repeating the verification idea) add a little length but keep the important information up front.

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 explaining the receipt (handles, volume/mass before and after, backup path). For a 9-parameter modeling tool it covers the critical decisions, though a few parameters such as shift and name are 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 78%, so it already documents most parameters. The description adds real value by tying path to the profile plane and sections to individual planes, but it does not explain shift, name, or closed semantics.

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 specific verbs and resources for both modes: kind=sweep moves a closed profile sketch along a path (pipes, springs, bent rods), kind=loft builds a body through 2+ section sketches (round-to-square transition). This lets an agent pick the right mode and distinguishes it from part_extrude/part_revolve work without inspecting schemas.

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 clear conditions for each kind, including concrete use cases and the constraint that a sweep path must start on the profile's plane and loft sections each need their own plane. It stops short of naming when to prefer a sibling such as part_extrude or part_revolve instead, so there is no explicit exclusion guidance.

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