Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Add position leaders

drw_add_positions

Add position leader callouts to an assembly drawing view. Shelves align in one column or row, ordered so leader lines never cross, and one Ctrl+Z undoes the whole set.

Instructions

Position leaders (ГОСТ 2.109) on an assembly drawing: shelves lined up in one column/row beside the view, ordered so the leader lines do not cross; one Ctrl+Z. Check 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>",
      "items": "<items>"
    },
    "name": "drw_add_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
gapNodistance between shelves, sheet mm
sideNoright
viewYesnumber of an associative view of the ASSEMBLY
itemsYesposition = number from spec_create rows; point = a model point on a VISIBLE face of that component (assembly coordinates, mm)
offsetNoshelf distance from the view, sheet mm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive write, so the description's job is to add what annotations cannot. It does: 'one Ctrl+Z' discloses that the whole batch is a single atomic undo unit, and the auto-layout rule ('shelves lined up ... ordered so the leader lines do not cross') describes derived behavior the agent cannot infer from the schema.

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?

A single dense sentence, front-loaded with the what, followed by the layout behavior, the undo guarantee, and the verification pointer. No filler; every clause carries information an agent cannot get from the structured fields.

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 6-parameter, non-idempotent drawing mutation with no output schema, the definition covers purpose, layout behavior, undo semantics and verification. What is left out is mostly prerequisite framing (obtaining a doc handle, that positions come from spec_create rows, that an associative assembly view is required), all of which is present in the schema rather than the description.

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 83%, so the schema already documents doc, view, items, point, shelf, gap, side and offset in detail. The description only loosely motivates the layout parameters by explaining that shelves are auto-arranged in one column/row, without adding meaning to 'position', 'side', 'gap' or 'offset' beyond what the schema states.

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 names a specific verb and resource ('Position leaders ... on an assembly drawing') and anchors it to the GOST 2.109 standard, which clearly separates it from drw_add_dimension, drw_add_section and drw_set_stamp. It stops short of naming a sibling to distinguish against, so it is clear but not explicitly differentiated.

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?

Usage is only implied: the assembly-drawing/GOST context tells an agent roughly where this belongs, and 'Check with view_capture' gives a post-call verification step. There is no statement of when to choose this over other drawing-annotation tools, no prerequisites (assembly associative view must exist), and no exclusions.

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