Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Inspect model

inspect_model
Read-onlyIdempotent

Produces a read-only KOMPAS-3D report covering feature trees, variables, mass properties, bounding boxes, errors, and review checklists to validate parts, assemblies, drawings, and specifications.

Instructions

Read-only report on a part/assembly: feature tree (object handles, validity, errors), variables (with tolerances), mass properties in mm/kg (fresh, never cached), bounding box, properties (designation/name/material), active embodiment, rebuild errors and default-named features. 'review' adds a deterministic checklist (broken features, default names, missing designation/name/ material, manual mass, variables without notes) — the basis of the review_model prompt. On a DRAWING (.cdw) the report is the drawing itself: sheets, views (number, scale, position, angle, source model, section), their dimensions (kind, value, tolerance, associative) and technical requirements; with 'review' it is cross-checked against its model (hand-typed dimension values, unbound dimensions, title block vs model properties/mass, scale, views off the sheet). On a SPECIFICATION 'review' compares its rows with the attached assembly's components and quantities (the assembly must be open). Leaves no Undo entry and does not mark the document as changed. Also clears NEEDS_REVIEW.

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

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
objNofeature obj: handle -> return only THAT feature: its internal variables (e.g. the depth of an extrusion, a hole's diameter with can_have_tolerance — bind them via variables_set) and its definition (kind, params, editable — change them via feature_edit(params=…))
pageNoTree page (200 features per page)
sectionsNoWhich parts of the report to build

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / obj / description
      Previous value: -"feature obj: handle -> return only THAT feature's internal variables (e.g. the depth of an extrusion, a hole's diameter with can_have_tolerance) — bind them via variables_set"New value: +"feature obj: handle -> return only THAT feature: its internal variables (e.g. the depth of an extrusion, a hole's diameter with can_have_tolerance — bind them via variables_set) and its definition (kind, params, editable — change them via feature_edit(params=…))"
    • changedInput schema / properties / sections / items / enum
      Previous value: -[
      -  "tree",
      -  "variables",
      -  "mass",
      -  "bbox",
      -  "properties",
      -  "embodiment",
      -  "errors",
      -  "naming",
      -  "review"
      -]New value: +[
      +  "tree",
      +  "variables",
      +  "mass",
      +  "bbox",
      +  "properties",
      +  "embodiment",
      +  "errors",
      +  "naming",
      +  "review",
      +  "components",
      +  "bodies",
      +  "sketches"
      +]
  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?

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that mass properties are fresh and never cached, that the operation leaves no Undo entry and does not mark the document changed, and that it clears NEEDS_REVIEW. It also explains what 'review' cross-checks on drawings and specifications, giving valuable behavioral context.

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?

The description is dense but front-loads the primary purpose and then organizes details by document type and review mode. It is appropriately sized for a complex multi-mode inspection tool, though some long clauses could be more scannable.

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?

Given the complexity of supporting parts, assemblies, drawings, and specifications with no output schema, the description is remarkably complete. It covers the report contents, review behavior, drawing cross-checks, specification requirements, and side effects an agent needs to know.

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?

The input schema has 100% description coverage and already explains doc, obj, page, and sections in detail. The tool description reinforces the report contents and review behavior but does not add substantial meaning beyond the schema for individual parameters.

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 description opens with a specific verb and resource: a read-only report on a part/assembly, and it extends that scope explicitly to drawings and specifications. It clearly distinguishes the normal report from the 'review' variant by describing what review adds.

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?

It gives clear usage context: use the base report for inspection, add 'review' for a deterministic checklist, and note that specification review requires the attached assembly to be open. It does not explicitly name sibling alternatives such as inspect_check or state when not to use this tool, so it falls 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.