Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

save_drawing

Save a drawing to its current location or a specified path, optionally choosing an AutoCAD format version for compatibility; returns the saved file path.

Instructions

Сохранить чертёж. Без пути: сохранить текущий или в папку вывода. version: год формата для старых версий AutoCAD (2018, 2013, 2010, 2007, 2004, 2000; можно год своей версии, например 2016). Возвращает путь к файлу.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
versionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/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 does disclose useful behavior: default target when path is absent, the accepted version years, and that a file path is returned. It omits important save semantics such as overwrite behavior, whether saving to a new path renames the active document, and any permission or failure conditions.

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?

Front-loaded with the action, then the default-path rule, then the version explanation, then the return value. Three short sentences with no filler, though the trailing return-value sentence duplicates what the output schema already conveys.

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?

The tool is simple (two optional parameters) and the description covers both defaults and the version enumeration, which is the main complexity. An output schema exists, so the return-value sentence is redundant, while more consequential gaps remain around overwrite and rename semantics for a save operation.

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 for both parameters. It does well on version, enumerating concrete years (2018, 2013, 2010, 2007, 2004, 2000) and noting that an arbitrary version year such as 2016 is accepted, but path is only described by its absence case, leaving unclear whether it is a file, a directory, or relative versus absolute.

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, which is unambiguous and fits alongside drawing-oriented siblings like open_drawing and new_drawing. It does not distinguish itself from siblings explicitly, but no sibling performs saving, so the risk of mis-selection is low.

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 clause "Без пути: сохранить текущий или в папку вывода" tells the agent what happens when path is omitted, which is actionable context. However, it never says when saving is appropriate versus other workflows (e.g., after which drawing operations), nor any prerequisite such as an open document, so guidance is implied rather than explicit.

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