Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

export_dxf

Export a copy of the drawing as DXF without altering the original file; if no path is given, saves to the output folder.

Instructions

Сохранить копию чертежа в DXF (текущий файл не меняется). Без пути: в папку вывода.

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description still discloses the most important trait: the current drawing file is not modified, making this a safe read-only style export. It also explains the default destination when no path is given. Gaps remain on overwrite behavior if the target file exists and on permission requirements.

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?

Two short, front-loaded sentences with no filler: the effect first, then the default-path behavior in parentheses.

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

Completeness5/5

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

For a one-optional-parameter export tool with an output schema already covering return values, the description covers viability, non-destructiveness, and the default destination. Nothing essential for correct invocation is missing.

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 the single 'path' parameter is undocumented in the schema, but the description compensates by explaining that omitting the path writes to the output folder. That is exactly the semantic an agent needs for the one optional argument.

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 ('Сохранить копию чертежа в DXF') and the format name alone distinguishes it from the export_pdf sibling. It does not explicitly name an alternative, but the operation is unambiguous.

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?

Implicit guidance: it is clearly the DXF export path, and the default-folder behavior is spelled out. There is no explicit when-to-use vs. when-not guidance (e.g., export_pdf vs export_dxf), so usage is only implied by the format.

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