Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

render_preview

Renders a PNG preview of an AutoCAD drawing on a light background so you can visually verify geometry; specify a rectangular area or the full drawing and receive the output file path.

Instructions

PNG-превью чертежа (светлый фон) для проверки результата. area [x1,y1,x2,y2] или весь чертёж. Возвращает путь к файлу.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
pathNo
width_pxNo

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, the description must carry the behavioral burden. It discloses the output format (PNG), the light background, and that a file path is returned, which implies a file is written to disk, but it never says whether the drawing itself is modified, whether the file is overwritten, or what permissions/locks are needed.

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?

Three short sentences, front-loaded with the purpose and output type; no filler. Slightly terse on the non-area parameters, but nothing is wasted.

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-shape detail is not required, and the description still mentions the file path. However, for a 3-parameter tool with 0% schema coverage, the meaning of path and width_px should have been addressed in the description.

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 description coverage is 0%, so the description must compensate. It does explain the format of area ([x1,y1,x2,y2]) and that omitting it renders the whole drawing, although path and width_px (default 1600) are left entirely to the schema titles.

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 names a specific verb+resource pair: renders a PNG preview of the drawing on a light background for checking the result. That clearly separates it from sibling exporters like export_pdf and export_dxf, which produce document formats rather than a quick image check.

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?

"for checking the result" implies the use case and the description states that an area can be given or the whole drawing rendered. It never explicitly contrasts with export_pdf/export_dxf or states when a preview is preferable to a full export, so guidance is implied rather than spelled out.

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