Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Create specification

spec_create
Destructive

Creates a GOST 2.106 specification (.spw) for a saved assembly, filling sections, positions, designations, names, and quantities from components and the title block.

Instructions

Specification (спецификация, ГОСТ 2.106) of a SAVED assembly: a new .spw with the assembly attached; KOMPAS fills the sections, positions, designations, names and quantities from the components and the title block from the assembly. Returns the rows (check them against asm_bom). Saved to path.

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": {
      "assembly": "<assembly>",
      "path": "<path>"
    },
    "name": "spec_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesnew .spw file (absolute, inside the allowed roots)
assemblyYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
overwriteNoreplace an existing file (only after the user agreed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds useful behavior: the file is newly generated, KOMPAS auto-fills sections/positions/designations/quantities plus the title block, and the tool returns the rows. It does not spell out what happens to an existing file when overwrite is set, leaving that to 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.

Conciseness4/5

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

Front-loaded with the core fact (new .spw from a saved assembly) and each clause carries content about generated sections and the return value. The parenthetical asides and mixed-language term make it slightly dense but not wasteful.

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 document-generating tool with no output schema, the description covers input prerequisite, what gets auto-populated, and what is returned (rows). It leaves minor gaps about overwrite consequences and whether the assembly must be open, but the essentials an agent needs are present.

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 100%, so all three parameters are already documented in the schema, including the overwrite safety note. The description adds only 'Saved to `path`', which restates schema information, 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 product: creates a new .spw specification (ГОСТ 2.106) from a SAVED assembly. It is clearly distinguishable from spec_edit (editing) and asm_bom (BOM listing), and explains what content KOMPAS populates automatically.

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 ('of a SAVED assembly') and a verification step ('check them against asm_bom'), which implicitly routes the agent to asm_bom for cross-checking. It never states when not to use it or how it relates to spec_edit, so it falls short of full alternative routing.

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