Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Create document

doc_create
Idempotent

Create a new unsaved KOMPAS document—part, assembly, drawing, or fragment—and make it active. Use doc_save to save it to a path chosen by the user.

Instructions

Create a new, unsaved KOMPAS document (default template) and make it active. Save it with doc_save(path=…) — ask the user where.

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": {
      "kind": "<kind>"
    },
    "name": "doc_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4/5.0
Behavior3/5

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

Adds useful behavior beyond the annotations: it creates an unsaved document from the default template and changes the active-document state, which is a side effect an agent must know about. It does not say what is returned (document name/id) or how templates are chosen. Note also a tension: the description implies each call spawns a new document, which sits awkwardly with the declared idempotentHint=true, though that is arguably an annotation issue rather than a description misstatement.

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?

Two short sentences, front-loaded with the core action and followed by the mandatory next step. Nothing is redundant or padded.

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 one-parameter creation tool with no output schema, this covers the essentials: what is created, its unsaved state, and how to persist it. Only the return value and any template/kind effects are left implicit.

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 0% and the single parameter 'kind' is never mentioned in the description. The enum values (part/assembly/drawing/fragment) are largely self-explanatory in the schema, and 'default template' hints at the default behavior, so the description does not need to do much more, but it adds no meaning about what each kind produces.

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 ('Create a new, unsaved KOMPAS document') plus the key qualifiers: default template and that it becomes active. An agent can distinguish this from doc_open or doc_save without opening any schema.

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?

Explicitly routes the follow-up to doc_save(path=…) and even says to ask the user where, which is real when-to-use guidance. It stops short of naming doc_open as the alternative for existing files, but the 'new, unsaved' wording implicitly excludes that path.

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