Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

export_pdf

Exports AutoCAD drawing sheets to PDF, including all sheets as one multipage file or a selected area/format/scale, with optional monochrome output.

Instructions

PDF. Без area/format печатает последний лист make_sheet в его масштабе; all_sheets=True: все листы make_sheet этого чертежа одним многостраничным PDF (по номерам листов). Иначе format (A4..A1), landscape, area [x1,y1,x2,y2] или весь чертёж, scale 1:N (0 = вписать). monochrome: чёрно-белый. COM: плоттер DWG To PDF.pc3; ezdxf: matplotlib.

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_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
pathNo
scaleNo
formatNo
landscapeNo
all_sheetsNo
monochromeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the default output, the multipage behavior, scale semantics (0 = fit), and notably the backend-dependent implementation (COM plotter DWG To PDF.pc3 vs ezdxf matplotlib). It omits overwrite/permission behavior for the output path, keeping it from a 5.

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?

Extremely dense and front-loaded, with every clause conveying real information and no filler. The telegram-style semicolon-separated structure and mixed Russian/English reduce readability but do not waste words.

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 7-param export tool with an output schema covering return values, this is nearly complete: default behavior, all_sheets, scale, format, area, monochrome, and both execution backends are covered. Missing output-path semantics and overwrite behavior are the remaining gaps.

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%, so the description must compensate and largely does: it defines area as [x1,y1,x2,y2], format range A4..A1, landscape orientation, scale 1:N with 0 = fit, all_sheets, and monochrome. Only the 'path' parameter is left unexplained, which is the main gap against a 7-param tool.

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?

The description makes clear this exports/prints a drawing to PDF and details the default mode (prints the last make_sheet sheet at its own scale). It is specific about resource and modes, though the verb is only implied by the terse 'PDF.' opener rather than stated 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?

It explains mode selection well: no area/format → last sheet; all_sheets=True → all sheets as multipage; otherwise format/area/landscape. This is really behavioral branching rather than when-to-use-vs-alternatives guidance; it never tells the agent when to pick PDF over export_dxf or other siblings.

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