Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Add component

asm_add_component

Insert a part or assembly file into a KOMPAS-3D assembly at its origin, optionally fix it, then position it with mates; failed checks restore the assembly.

Instructions

Insert a part/assembly file into an assembly at its origin. Then position it with asm_mate (the first component is usually fixed=true). Component list and boxes: inspect_model(sections=['components']). Returns a receipt; one Ctrl+Z for the user; on a failed check the assembly is restored (VERIFY_FAILED).

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>",
      "path": "<path>"
    },
    "name": "asm_add_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesAssembly document handle
pathYesabsolute .m3d/.a3d path inside the allowed roots
fixedNofix the component in place

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say non-read-only, non-idempotent, non-destructive) by disclosing that it returns a receipt, that undo is a single Ctrl+Z, and that a failed verification restores the assembly with VERIFY_FAILED. For a mutation tool this is exactly the transactional and rollback context an agent needs.

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?

Front-loads the action in the first sentence and every subsequent clause carries distinct information (placement follow-up, inspection sibling, return value, undo, failure mode). The telegraphic 'one Ctrl+Z for the user' phrasing is terse enough to require a re-read, which keeps it from a 5.

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 3-parameter mutation tool with no output schema, the description covers the action, the follow-up step, how to discover valid inputs, what is returned, and what happens on failure. Nothing an agent needs before calling it 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 coverage is 100%, so the baseline is 3, and the description adds real meaning by saying the first component is usually fixed=true, which explains the practical use of the `fixed` flag rather than repeating its definition. It adds nothing on `doc` or `path`, but those are already fully documented.

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 a specific verb and resource: 'Insert a part/assembly file into an assembly at its origin.' It also implicitly scopes itself away from positioning by delegating that to asm_mate, so an agent can tell it apart from the mate/placement siblings.

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 a clear workflow: call this first, then position with asm_mate, with a note that the first component is usually fixed=true, and points to inspect_model(sections=['components']) for the component list. It gives no explicit when-not-to-use or error-recovery routing, so it stops short of a 5.

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