Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

set_engine

Switch drawing backend between live AutoCAD COM and standalone ezdxf, or auto-select the available engine to control whether drawings require AutoCAD.

Instructions

Переключить движок: 'auto' (COM если есть, иначе ezdxf), 'com' (живой AutoCAD) или 'ezdxf' (без AutoCAD).

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": {
      "engine_name": "<engine_name>"
    },
    "name": "set_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
engine_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/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, and it does disclose meaningful behavior: that 'auto' falls back, and that 'com' requires a live AutoCAD while 'ezdxf' does not. It omits whether the setting persists across calls, whether 'com' errors when AutoCAD is absent, and whether switching engines mid-session affects existing objects.

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?

One compact sentence that front-loads the action and then the option list; every clause (including the parenthetical fallback rule for 'auto') carries information an agent needs.

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 single-parameter tool with an output schema, the definition covers the one thing the schema leaves blank — the allowed values and their semantics. Only persistence and error behavior remain unspecified, which are secondary for a mode toggle.

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 0% and there is no enum, so the description must supply the valid values — and it does, listing all three accepted strings with their meanings. It does not state case sensitivity, whitespace, or what happens with an unrecognized value, so it stops short of full compensation.

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 ('Переключить движок' / switch the engine) and enumerates the three modes, so an agent knows exactly what changes. It does not need to distinguish itself from siblings like set_layer or set_profile, which act on different resources, but it also does not explicitly say so.

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 gloss for each mode ('auto' = COM if available else ezdxf, 'com' = live AutoCAD, 'ezdxf' = without AutoCAD) implies when each is appropriate, letting an agent infer 'use com when AutoCAD is running, ezdxf otherwise'. However, there is no explicit when-to-use recommendation, no statement of which mode is the default, and no guidance on switching back or on failure.

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