Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Part properties

part_set_properties

Set a KOMPAS-3D part's designation and name so the title block and BOM update associatively. Each call is backed up, verified, and undone with a single Ctrl+Z.

Instructions

Set the part's designation (обозначение, ГОСТ Р 2.201) and name (наименование) in the MODEL, so the title block and the BOM follow them associatively. Never invent a designation: take it from the user. 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>"
    },
    "name": "part_set_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
nameNoнаименование, e.g. 'Фланец'
markingNoобозначение, e.g. 'АБВГ.711141.001'
material_idNomaterial from select(kind='material') — taken earlier from KOMPAS's handbook via material_pick; free text is never accepted. Not undoable by Ctrl+Z: the receipt has restore_material_id
spec_sectionNospecification section of a PART file: standard = «Стандартные изделия» (a ready fastener file; its full name with the standard goes into `name`, designation empty). Not undoable by Ctrl+Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / spec_section
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "detail",
      +        "standard",
      +        "other"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "specification section of a PART file: standard = «Стандартные изделия» (a ready fastener file; its full name with the standard goes into `name`, designation empty). Not undoable by Ctrl+Z",
      +  "title": "Spec Section"
      +}
  2. First observedv0.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the receipt contents (handles, volume/mass before and after, backup path), the single-Ctrl+Z undo model, and the restore-plus-VERIFY_FAILED path on verification failure. The claim 'The whole call is ONE Ctrl+Z' overstates coverage, since the schema records that material_id and spec_section changes are not undoable by Ctrl+Z — a real inconsistency with structured data that keeps this from a 5.

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?

Three tight sentences, front-loaded with the action and its effect, then guardrails, then return/undo behavior. Dense but every sentence carries information; only the blanket 'whole call is ONE Ctrl+Z' phrasing is wasteful because it misleads.

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?

For a mutation tool with no output schema and full schema coverage, the description covers return value, undo semantics, and failure handling — what an agent needs before calling it. It leaves the material_id and spec_section parameters entirely to the schema, and its undo statement is broader than the schema's per-parameter caveats.

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 100%, so the baseline is 3. The description maps designation to обозначение and name to наименование, but the schema already carries those glosses and examples; the one genuine addition, that the designation must be sourced from the user, is guidance rather than parameter 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 a specific verb (Set) and resource (the part's designation and name in the MODEL), plus the downstream effect: the title block and BOM follow them associatively. Combined with the ГОСТ Р 2.201 and наименование qualifiers, this is unambiguous and not confusable with model-building siblings such as part_body or variables_set.

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 real usage constraint — 'Never invent a designation: take it from the user' — which tells the agent what input is acceptable. It does not name an alternative tool or state when-not-to-use, 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.