Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Pick material in KOMPAS

material_pick

Opens KOMPAS's material handbook dialog so you can choose a material, then optionally assigns it to a part with backup and mass check.

Instructions

Open KOMPAS's own material handbook dialog so the USER chooses the material (the handbook is the source of truth for name and density). Tell the user the dialog is open and wait. If doc is given, the material is assigned to the part with a backup and a mass check (receipt). NOTE: KOMPAS does not record material changes in Undo (Ctrl+Z will not revert it); to revert call part_set_properties(material_id=restore_material_id). The choice is remembered: later part_set_properties(material_id=…) assigns it without the dialog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "material_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
docNoIf given, assign the picked material to this part

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.8/5.0
Behavior5/5

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

Adds behavior the annotations do not cover: the call is interactive and requires waiting for the user, changes bypass KOMPAS's undo stack, and an assignment produces a backup and mass-check receipt. The undo caveat is important context beyond readOnlyHint/destructiveHint flags.

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?

The interactive step is front-loaded and the revert guidance follows logically. The parenthetical '(receipt)' is slightly cryptic, but overall there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an interactive, non-idempotent tool with one optional parameter, the description covers the user-wait loop, the assignment side effects, the undo limitation, and the revert procedure. Nothing an agent needs in order to call it correctly 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 schema already defines `doc`. The description still adds meaning by saying what assignment actually does beyond the schema's one-line note: backup plus mass check.

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: it opens KOMPAS's material handbook dialog so the user picks the material. It also distinguishes itself from part_set_properties by explaining that the later call assigns the remembered choice without a dialog.

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?

Gives explicit when-to-use (user must choose from the handbook, the source of truth), what the optional `doc` triggers (assignment plus backup and mass check), and the exact revert path via part_set_properties(material_id=restore_material_id). It also warns that Ctrl+Z will not undo the change.

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