Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Move / scale view

drw_view_edit

Edit a drawing view's scale, position, rotation, or name in one undoable change while preserving dimension values, and warn when the view extends beyond the sheet.

Instructions

Change a drawing view: scale, position, rotation, name — one Ctrl+Z; dimensions keep their values. Warns when the view then sticks out of the sheet. Check the layout with view_capture.

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

Input Schema

NameRequiredDescriptionDefault
xNoview origin on the sheet, mm
yNoview origin on the sheet, mm
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
nameNo
viewYesview number (inspect_model on the drawing lists them)
angleNorotation, degrees counter-clockwise
scaleNo0.5 = 1:2, 2 = 2:1 (ГОСТ 2.302 scales)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (not read-only, not destructive, not idempotent). The description adds genuinely new behavioral facts: the change is a single undo step ("one Ctrl+Z"), dimensions retain their values after the edit, and the tool emits a warning when the view overflows the sheet. Those are exactly the side-effect and return-signal details an agent needs before mutating a drawing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation and its editable fields, followed by the consequence and the verification hint. Nothing is redundant or padded.

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 reversibility, side effects, and the warning behavior well. The one remaining gap is that it never says whether omitted optional parameters leave the corresponding property unchanged, which matters for a 7-parameter partial-update call.

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 86%, so the schema already documents units, ranges, and the meaning of each parameter. The description adds no syntax or constraint detail beyond grouping the fields into scale/position/rotation/name, so the baseline of 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?

The description names a specific verb and resource ("Change a drawing view") and enumerates the editable aspects: scale, position, rotation, name. That set maps cleanly onto the schema properties (scale, x/y, angle, name), so an agent can tell this apart from sibling tools such as view_capture or drw_create_views without opening the schema.

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 intended usage is implied: it modifies an existing view, and "Check the layout with view_capture" gives a follow-up verification path. However, the description never states when to use this instead of creating new views or other edit tools, and it offers no exclusion or prerequisite conditions.

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