Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

import_order

Imports K-Zamer order JSON or backup files, builds all ordered products and a specification in AutoCAD, and lets you select which backup order to place.

Instructions

Импорт заказа из «К-Замер»: data = JSON заказа {customer, items:[{templateId, values}]}, файл резервной копии {app:'k-zamer', orders:[...]} или путь к .json. Строит все изделия и спецификацию. order_index: какой заказ из бэкапа (по умолчанию все, друг под другом).

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": {
      "data": "<data>"
    },
    "name": "import_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
dataYes
order_indexNo
text_heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the material side effect that all products and the specification are built. However, it does not say what happens on malformed input, whether existing objects are replaced or duplicated, or what x/y/text_height do to placement, leaving significant behavioral gaps.

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?

The description is compact and front-loads the core action and the primary input format, with the order_index note placed last where it belongs. The nested brace notation makes it read as a dense run-on, 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?

Return values need not be described because an output schema exists, and the description covers the mutation effect and the primary input contract adequately for a five-parameter import tool. The unaddressed coordinate and text-height parameters, plus the absence of error/collision behavior, are the remaining gaps.

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 0%, so the description must compensate. It does add real meaning beyond the schema for the required 'data' parameter by spelling out the nested shape {customer, items:[{templateId, values}]} and the backup structure, and it explains order_index and its default. It says nothing about x, y, or text_height, leaving three of five parameters undocumented anywhere.

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?

States a specific verb and resource ('Импорт заказа из «К-Замер»') and adds the concrete effect, building all products and the specification. It is clearly an import-style operation, which contrasts implicitly with drawing siblings such as draw_order, but it never names or contrasts them directly.

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 description explains the accepted input shapes (order JSON, backup file object, or a path to a .json), which tells an agent when this tool applies, and clarifies order_index semantics including the 'all orders' default. It gives no explicit exclusions or guidance on choosing this over draw_order or other creation tools.

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