Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Bill of materials

asm_bom
Idempotent

Generates a top-level assembly bill of materials grouped by GOST 2.106 sections with designation, name, quantity, and material; optionally exports to .xlsx for checks or drafts.

Instructions

Bill of materials of an assembly (top level) grouped by ГОСТ 2.106 sections: Сборочные единицы, Детали, Стандартные изделия — designation, name, quantity, material. Optionally written to .xlsx. This is NOT a KOMPAS specification document (.spw): use it as a check or a draft.

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

Input Schema

NameRequiredDescriptionDefault
docYesAssembly document handle
xlsx_pathNoalso write an .xlsx (inside the allowed roots); existing files are not replaced

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 declare readOnlyHint=false, idempotent=true, destructive=false, and the description is consistent with a read-plus-optional-xlsx-export tool. Beyond annotations it discloses the grouping standard, the fields returned, and the important behavioral caveat that the output is a draft/check rather than a compliant spec. Missing are things like whether the assembly must be open or what happens on write failure, which the schema partially covers.

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?

Three tight sentences, front-loaded with what the tool produces, then the output option, then the .spw exclusion. No filler; only minor redundancy between 'Optionally written to .xlsx' and the schema's xlsx_path description.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their section grouping. Combined with a fully documented 2-parameter schema, an agent has enough to invoke it correctly; only operational prerequisites are unstated.

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% and both parameters (doc, xlsx_path) are documented in the schema, so the baseline is 3. The description only restates that .xlsx writing is optional and does not add syntax, format, or path constraints beyond the schema.

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+resource: bill of materials of an assembly (top level), grouped by ГОСТ 2.106 sections, with the exact fields produced (designation, name, quantity, material). It also explicitly distinguishes itself from a KOMPAS specification document (.spw), so an agent can tell it apart conceptually from spec-generation flows.

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 clear context: it can be used as a check or a draft, and is NOT a .spw specification. That frames when to reach for it versus a real spec. It stops short of naming a specific alternative tool or stating prerequisites (e.g., assembly must be open), so it is strong but not a full when/when-not/alternatives statement.

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