Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Extrude

part_extrude

Create boss or cut extrusions from a sketch, with verified volume changes, a backup, and undo in a single step. Rejects cuts that remove no material.

Instructions

Boss or cut extrusion of a sketch. Verified: boss must add volume, cut must remove it; a cut that goes away from the material is rejected (then try direction='reverse'). 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_extrude"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoboss
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
nameNoMeaningful feature name for the tree, e.g. 'Отв_крепёжные_6xD11'
depthNomm (ignored with through=true)
depth2Nosecond side depth for direction='both'
sketchYesobj: handle from inspect_model/receipt, or '$N' inside batch
throughNothrough all (cut)
new_bodyNoboss as a SEPARATE body (multi-body part, then part_body)
directionNonormal

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 (multi-body part, then part_body)",
      +  "title": "New Body",
      +  "type": "boolean"
      +}
  2. First observedv0.4.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare it is not read-only and not destructive; the description goes far beyond that by disclosing the built-in verification contract (boss must add volume, cut must remove it), the rollback behavior on failure (model restored, VERIFY_FAILED returned), and the single-undo transactional guarantee. It also previews the receipt contents (handles, before/after volume and mass, backup path), which is exactly the behavioral context an agent needs before invoking a mutation.

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?

Three tightly packed sentences, front-loaded with what the tool does and followed by the verification contract and the receipt/failure behavior. There is no filler, no restatement of the name, and the recovery hint is placed immediately after the rule it remedies.

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 nine parameters, no output schema, and mutation semantics, the description supplies the return shape, the failure mode, and the rollback guarantee that the schema cannot express. The remaining gap is minor: a few secondary parameters (new_body, depth2, through) rely entirely on schema text, but nothing essential to calling the tool correctly is 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 description coverage is 78%, so the schema carries most parameter meaning and the baseline would be 3. The description adds genuine value by explaining the causal link between cut direction and the reverse direction setting, which is not derivable from the enum alone, and by framing the verification outcome the parameters produce. It does not explain new_body, depth2, or through, leaving those to the schema.

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 opening sentence gives a specific verb and resource ('Boss or cut extrusion of a sketch'), which immediately separates it from siblings like part_revolve or part_sweep_loft. It also names the two operating modes (boss, cut) and their semantics, so an agent can decide whether this is the right feature operation without opening the schema.

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?

Guidance is present but focused on failure recovery rather than selection: it tells the agent that a cut removing no material is rejected and to retry with direction='reverse'. There is no explicit statement of when to choose extrusion over revolve/sweep/loft, nor prerequisites beyond the sketch handle. Usage is implied by the domain rather than spelled out.

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