Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Capture view

view_capture
Read-onlyIdempotent

Capture a PNG snapshot of a KOMPAS document as rendered, optionally using a standard orientation or fit-to-view for that image while restoring the user's current view afterward.

Instructions

PNG image of the document as KOMPAS renders it. By default the user's current view; view/fit turn the view for this snapshot only — the user's orientation and zoom are restored right after (they may see a short flicker). Front = XY plane (ГОСТ 2.305 главный вид), top = ZX.

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

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
fitNozoom to show everything
sizeNoApprox. width px
viewNo3D models: standard orientation for this snapshotcurrent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / fit
      Added value: +{
      +  "default": false,
      +  "description": "zoom to show everything",
      +  "title": "Fit",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "default": "current",
      +  "description": "3D models: standard orientation for this snapshot",
      +  "enum": [
      +    "current",
      +    "front",
      +    "back",
      +    "top",
      +    "bottom",
      +    "left",
      +    "right",
      +    "iso",
      +    "dimetric"
      +  ],
      +  "title": "View",
      +  "type": "string"
      +}
  2. First observedv0.4.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real behavior the annotations cannot convey: view and fit alter orientation only for the snapshot, then the user's orientation and zoom are restored, possibly with a brief visible flicker. That side-effect disclosure is exactly the kind of context an agent needs before invoking a 'read-only' tool that visibly perturbs the user's screen.

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 dense sentences, front-loaded with the output type and then the mutation caveat. Phrasing is telegraphic in places ("view/fit turn the view") and the ГОСТ reference could be trimmed, but no sentence is wasted.

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, the description carries the return type (PNG), the side-effect semantics, and the orientation mapping — enough for correct invocation of a four-parameter read tool. Minor gaps remain around error behavior and how size interacts with the rendered output.

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 baseline is 3, but the description adds meaning the enum alone lacks: front maps to the XY plane (ГОСТ 2.305 main view) and top to ZX, plus the crucial note that view/fit are snapshot-scoped. It does not clarify the size/approximate-width tradeoff, but it clearly exceeds the schema.

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 concrete verb and resource: it renders the document to a PNG image as KOMPAS draws it. That distinguishes it from file-oriented siblings such as export, but it never names or contrasts any alternative, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"By default the user's current view" implies the common case and the view/fit override, giving some usage context. However, there is no explicit statement of when to prefer this over export or drw_create_views, and no prerequisites or exclusions are given.

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