Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Rebuild drawing

drw_rebuild

Reopens a saved drawing after its model changes so associative views and dimension values update to the saved model; returns changed and unbound dimensions. Save the model first.

Instructions

Update a saved drawing after its model changed: reopens it so the associative views AND dimension values follow the saved model (answers KOMPAS «Перестроить чертеж?» with «Да»). Save the model first. Returns the dimensions whose values changed and unbound_dimensions: dimensions whose edge/face the model change replaced (e.g. a cut makes a new end face) lose their binding and keep the OLD value while the view is up to date — delete and re-add them with drw_add_dimension, or tell the user.

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": "drw_rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
saveNosave unsaved drawing changes first (only after the user agreed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing that the tool reopens the document, answers the KOMPAS 'Перестроить чертеж?' dialog with 'Да', and returns both changed dimensions and an `unbound_dimensions` set. It also explains the non-obvious failure mode — dimensions whose edge/face was replaced keep their OLD value even though the view is up to date — which is exactly the kind of subtle behavior an agent must anticipate.

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 core action and its precondition, then the return-value caveat. The parenthetical quoting the localized dialog prompt is slightly verbose but genuinely disambiguates which dialog the agent will trigger, so almost every clause earns its place.

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 carries the burden of explaining returns and does so explicitly (changed dimension values plus `unbound_dimensions` with its semantics). For a 2-parameter, non-idempotent mutation that shows a modal dialog, nothing essential is missing.

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%: `doc` is fully explained as a handle from doc_list/doc_open, and `save` already carries 'only after the user agreed'. The description only reinforces ordering ('Save the model first'), adding little meaning beyond the schema, so the baseline 3 applies.

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 ('Update a saved drawing after its model changed') plus the mechanism ('reopens it so the associative views AND dimension values follow the saved model'). This clearly separates it from drw_add_dimension or drw_view_edit, which operate on individual dimensions or view settings rather than re-associating the whole drawing to the model.

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 precondition ('Save the model first') and a conditional remediation path that names a sibling tool: unbound dimensions should be deleted and re-added with drw_add_dimension, or reported to the user. It does not state when NOT to rebuild (e.g. no-op case when nothing changed), so it falls short of full when/when-not coverage.

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