Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

open_drawing

Open an existing DWG or DXF drawing from an absolute file path so AI assistants can inspect or edit it in AutoCAD or with ezdxf.

Instructions

Открыть существующий чертёж (DWG для COM / DXF для ezdxf) по абсолютному пути.

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": {
      "path": "<path>"
    },
    "name": "open_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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 supplied, the description carries the full burden, and it does disclose one real behavioral trait: the backend is selected by file format (COM for DWG, ezdxf for DXF). It does not say what happens to an already-open drawing, whether the session is replaced, or how failures and unsupported formats are reported.

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 sentence, front-loaded with the action and resource, with the format/backend detail appended. Nothing is redundant and no prior context is needed to parse it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a state-changing entry-point tool with no annotations, though, the definition leaves open how it interacts with the current session and how errors surface, which is more than minor for an agent choosing to call it.

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 schema's single 'path' property is undocumented on its own. The description compensates partially by requiring an absolute path, and it implies the format is derived from the file, but it never states that the extension decides which backend is used or what extensions are accepted.

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 (open an existing drawing) and adds a scope qualifier (existing, absolute path) plus the format/backend pairing (DWG→COM, DXF→ezdxf). This implicitly separates it from new_drawing and save_drawing, though no sibling is named 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 word 'existing' implies this is the entry point for a drawing that already exists, as opposed to new_drawing, so usage is inferable. However, there is no explicit when-to-use statement, no prerequisite note (e.g. must be called before any draw_* operation), and no mention of an alternative for creating a drawing.

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