Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Set variables

variables_set

Create or update part variables and bind feature parameters to them in a parametric model, with verification and a single-step undo if changes fail.

Instructions

Create/change part variables and bind feature parameters to them (parametric model). 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>",
      "items": "<items>"
    },
    "name": "variables_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
itemsYes[{name, value? | expr?, note?, obj?, tolerance?}]. Without obj: part variable (created if missing; latin meaningful name, Russian note). With obj: an existing feature variable gets expr, e.g. 'H', 'D/2'. tolerance (feature variables with can_have_tolerance only, e.g. a hole's diameter): a field like 'H7'/'h6' — deviations are taken from KOMPAS's tolerance table for the variable's value — or {upper, lower} in mm; null removes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnly=false, idempotent=false, destructive=false). The description goes well beyond that: it specifies the return receipt contents (object handles, volume/mass before and after, backup path), the undo semantics (the whole call is ONE Ctrl+Z), and the failure path (model restored, VERIFY_FAILED returned). Those are exactly the behavioral traits an agent cannot get from structured fields.

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 sentences, front-loaded with the action, then the return shape, then the transactional guarantee. No filler or restatement of the title. It is dense with domain terms (receipt, backup path, VERIFY_FAILED) but each clause carries distinct information.

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, the description covers the return values, the atomicity guarantee, and the failure behavior — the pieces an agent most needs. The remaining gap is comparative routing: it never says when to prefer this over feature_edit or part_set_properties for changing a parameter.

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 description coverage is 100%, so the schema already documents doc and the items object with its name/value/expr/note/obj/tolerance fields and the H7/h6 tolerance table rule. The description text itself adds no parameter detail beyond what the schema supplies, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource pair: 'Create/change part variables and bind feature parameters to them (parametric model)'. That is far more precise than the title's 'Set variables', and the parenthetical names the domain (parametric modeling). It stops short of explicitly distinguishing itself from neighbors such as part_set_properties or feature_edit, so it lands at 4 rather than 5.

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?

The two modes (part variable without obj, feature-variable binding with obj) are explained, which implies when each path applies. However, there is no explicit when-to-use statement, no exclusion of alternatives like part_set_properties, and no stated prerequisites for binding a feature parameter. Usage is inferable but not guided.

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