Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Open document

doc_open
Idempotent

Open KOMPAS-3D documents from allowed roots, read-only by default, and import STEP/IGES files into a new millimeter model without modifying the source.

Instructions

Open a KOMPAS document (.m3d/.a3d/.cdw/.frw/.spw) from an allowed root. Opens read-only by default. Returns the document handle. If the file is already open, returns its existing handle. STEP/IGES (.stp/.step/.igs/.iges) are IMPORTED: a new model in mm is created from a temporary copy (the source is never modified); the answer has import.source_units read from the file header (e.g. inch), the bounding box in mm and the imported bodies. Imported bodies have no feature history.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path inside the allowed roots
read_onlyNoOpen read-only (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the returned handle, the idempotent reuse of an existing handle, the default read-only mode, and for imports the temporary-copy/never-modifies-source guarantee, unit normalization from the file header, and loss of feature history. Those are exactly the side effects an agent needs to predict outcomes.

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-loaded with the core action and handle behavior, then the import caveat, with no filler sentences. Slightly dense parenthetical enumeration of extensions, but every line carries information.

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?

With no output schema, the description compensates by describing the return value (handle) and the shape of import results (source_units, bounding box in mm, bodies). For a 2-parameter tool with full annotation coverage, nothing an agent needs to call it 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 coverage is 100%, so baseline is 3, but the description adds real meaning the schema lacks: which file formats `path` accepts and that `read_only` defaults to the safe mode. The only gap is that it does not discuss what happens if `read_only` is set false for an import.

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 ('Open') plus the resource and even enumerates accepted extensions (.m3d/.a3d/.cdw/.frw/.spw), which cleanly separates it from doc_create and doc_list. It also pre-empts the surprising case where .stp/.igs paths are imported rather than opened.

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 the operative condition ('from an allowed root') and the default behavior ('opens read-only by default'), plus a clear routing rule that STEP/IGES inputs take the import path. It does not explicitly name doc_create for new documents or state when to prefer that alternative, so it falls short of a full when/when-not treatment.

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