Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Technical requirements

drw_tech_requirements

Replaces a drawing’s technical requirements with specified lines and sets general roughness, then reads back the updated requirements.

Instructions

Replace the drawing's technical requirements (технические требования) with these lines and/or set the general roughness; read back. Heat treatment, coating, unspecified tolerances come from the user — a 3D model does not hold them.

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

Input Schema

NameRequiredDescriptionDefault
docYesDocument handle from doc_list/doc_open, e.g. 'doc:12001:0a1b2c3d'
linesNonumbered lines, e.g. '1. * Размеры для справок.'
general_roughnessNoнеуказанная шероховатость in the top right corner: {text: 'Ra 6,3', method: removal|no_removal|any, add_sign: true = «(√)»} — values from the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the agent already knows this is a non-idempotent write. The description adds real context beyond that: it replaces (not appends) existing content, it reads back the result, and certain data cannot be derived from the 3D model and must be supplied by the user. It does not say what happens to existing lines on partial replacement or whether doc_open is required first.

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?

Two compact sentences with the mutation and read-back front-loaded, followed by the domain caveat. The Russian term in parentheses aids disambiguation; nothing is padded, though the second sentence is slightly elliptical.

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 three-parameter write tool with no output schema, fully documented parameters and annotations covering the safety profile, the description covers the essential behavior and the key domain constraint. It could still state the effect of omitting one of the two optional fields.

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 100%, so the schema already explains doc handles, numbered line format and the general_roughness object shape. The description adds only the 'and/or' combination semantics and the domain caveat that roughness values come from the user, which is marginal but real added meaning.

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?

Uses a specific verb+resource pair: 'Replace the drawing's technical requirements' plus 'set the general roughness', and adds 'read back' to indicate it returns the resulting state. It is clear what the tool does, though it never names a sibling (e.g. drw_set_stamp) to distinguish itself explicitly.

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?

The 'and/or' phrasing implies at least one of lines or general_roughness must be supplied, and the note that heat treatment, coating and unspecified tolerances 'come from the user' signals a prerequisite the agent must satisfy. There is no explicit when-to-use vs. when-not guidance or reference to alternatives.

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