Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Fill title block

drw_set_stamp

Fills empty KOMPAS title-block cells that lack model sources and reads values back; for associative fields, set them via model tools then refresh views.

Instructions

Fill title-block (основная надпись) cells that have no source in the model. In a drawing with associative views, name/designation/material/mass come from the model and are refused — set them with part_set_properties / material_pick and call this with refresh=true. Values are read back.

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>",
      "cells": "<cells>"
    },
    "name": "drw_set_stamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
cellsYes{cell: text}. cell = KOMPAS cell number ('110') or alias: name, designation, material, mass, scale, sheet, sheets, organization, developer, checker, tech_control, norm_control, approved, *_date. Empty {} only reads the current values.
sheetNosheet index
refreshNorebuild views so associative cells update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the generic write/idempotency profile; the description adds substantive behavior: model-linked cells are 'refused' rather than overwritten, refresh rebuilds views so associative cells update, and results are read back. This explains why the tool is not idempotent. Minor gap: it doesn't say whether refusals raise an error or are silently skipped.

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?

Three tight sentences, front-loaded with the operation and its scope constraint, then the exception, then the remedy and read-back confirmation. The parenthetical Russian term adds local value for KOMPAS users without padding the text.

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 4-parameter mutation tool with a nested alias map and no output schema, the description covers safety-relevant behavior, the read path, and the refresh side effect. It could be slightly fuller on failure semantics for refused cells and multi-sheet scope, but nothing essential to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description meaningfully adds: it clarifies which of the documented aliases (name, designation, material, mass) are actually rejected in associative drawings, and it explains the purpose of refresh (associative cell updates) rather than just repeating the schema text.

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 ('Fill title-block cells') plus its scoping constraint: only cells 'that have no source in the model'. That constraint distinguishes it from part_set_properties and material_pick, which handle model-sourced fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: for associative drawings, name/designation/material/mass must go through part_set_properties / material_pick, then this tool is called with refresh=true. It also documents the read-only path via empty {} ('Empty {} only reads the current values'), giving both when-to-use and when-not-to-set.

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