Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

KOMPAS status

kompas_status
Read-onlyIdempotent

Retrieve KOMPAS-3D connection and environment status: version, licence, open dialogs, worker state and security policy. Call first and after any error to diagnose issues.

Instructions

Connection and environment status: KOMPAS version/build/PID, licence variant, open modal dialog, worker state (generation, restarts, documents flagged needs_review) and the effective security policy (managed/unmanaged/untrusted, profile, roots). Call this first and after any error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already pin the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), so the description earns credit for adding the return content and its diagnostic intent. The mention of an open modal dialog and worker restarts/needs_review flags conveys operationally important state an agent would otherwise not anticipate; only latency or failure-mode behavior is unaddressed.

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 resource, followed by a compact enumeration and one imperative sentence; essentially no filler. The field list is dense but each item (licence, modal dialog, worker state, policy) carries distinct diagnostic value.

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?

With no output schema and zero parameters, the description must describe what comes back, and it does so field-by-field. It is nearly complete for a status probe; it only omits what the response looks like when the connection itself is unavailable.

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?

The tool takes no parameters, so there is nothing to disambiguate and the baseline applies. The description does not need to add argument meaning here.

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?

Names a concrete resource (connection/environment status) and enumerates exactly what it exposes: KOMPAS version/build/PID, licence variant, open modal dialog, worker state, and effective security policy. That level of specificity makes it clearly distinct from job/worker siblings such as job_status, which reports task progress rather than environment and licence state.

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?

"Call this first and after any error" is an explicit, actionable usage rule that tells the agent both the entry point and the recovery path. It stops short of naming when to prefer a sibling (e.g. job_status for a running job), so no explicit exclusions are given.

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