Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Get user selection

selection_get
Read-onlyIdempotent

Retrieves the object, face, edge, or feature currently selected in KOMPAS-3D so you can resolve ambiguous selectors after asking the user to click the target.

Instructions

What the user has currently selected in KOMPAS (faces/edges as topo handles, features as obj handles). Use this when a selector is ambiguous: ask the user to click the object, then call this.

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

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuine context beyond them: the handle types returned and the human-interaction step required before calling. It does not say what happens when nothing is selected (empty result vs error), which is the main remaining gap.

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 tight sentences with the return shape front-loaded and the usage trigger immediately after. No filler or repetition of the tool name.

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, no-output-schema tool, the description compensates by disclosing what the returned handles represent and the interaction prerequisite. Only the empty/no-selection behavior and the relationship to 'select' are left 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 coverage is 100% and the single 'doc' parameter is fully documented in the schema, including an example handle format. The description adds no further meaning about the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('what the user has currently selected') and even enumerates the return shapes (faces/edges as topo handles, features as obj handles). It is clear what the tool yields, though it does not explicitly contrast with the sibling tool 'select'.

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?

It gives a concrete when-to-use trigger ('when a selector is ambiguous') plus an actionable workflow (ask the user to click the object, then call this). It stops short of naming alternatives such as 'select' or stating when not to use it.

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