Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

make_sheet

Create a GOST-compliant A4–A1 sheet with frame, title block, and optional side stamp around an area or whole drawing for PDF export.

Instructions

Лист: рамка формата A4/A3/A2/A1 (landscape) в модели в масштабе 1:scale (0 = подобрать) вокруг области area [x1,y1,x2,y2] или всего чертежа, с основной надписью ГОСТ 2.104 (форма 1): title (наименование), number (обозначение), developer, checker, date, organization, sheet/sheets. side_stamp: дополнительные графы на левом поле (Инв. № подл., Подп. и дата, Взам. инв. №, Перв. примен.) и «Копировал / Формат» под рамкой. После него export_pdf без параметров печатает этот лист, export_pdf(all_sheets=True) все листы чертежа одним PDF.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
dateNo
scaleNo
sheetNo
titleNo
formatNoA3
numberNo
sheetsNo
checkerNo
developerNo
landscapeNo
side_stampNo
organizationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/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 well: it discloses the created content (frame, GOST 2.104 form 1 title block, sheet/sheets numbering) and the side_stamp effect — extra left-margin columns (Инв. № подл., Подп. и дата, Взам. инв. №, Перв. примен.) plus a "Копировал / Формат" block under the frame. It also reveals downstream behavior for printing. It does not say what happens on repeated invocation or whether an existing frame is replaced, which keeps it below 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?

Front-loaded with the artifact ("Лист:") followed by format/scale/area scope, then title-block fields, then side_stamp, then the export_pdf follow-up — a logical order with no filler sentences. The middle is a single very dense run-on clause, which costs some readability, but almost every word carries required information given 13 undocumented parameters.

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 13-parameter geometry/mutation tool with no annotations, the description covers what is created, where it is placed, all parameter meanings, and the printing follow-up; the presence of an output schema removes the need to explain return values. Remaining gaps are edge-case behavior (redraw/replace semantics, area coordinate units or coordinate-space assumptions) rather than anything blocking a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, so the description must compensate entirely, and it does: it names format options (A4/A3/A2/A1), landscape, scale with the special "0 = подобрать" sentinel, area as [x1,y1,x2,y2], title/number/developer/checker/date/organization as title-block fields under ГОСТ 2.104, sheet/sheets as page numbering, and side_stamp semantics. Every parameter receives meaning that the schema's bare titles and defaults do not supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Лист: рамка формата A4/A3/A2/A1 ... с основной надписью ГОСТ 2.104") and states exactly what artifact is produced — a drawing frame with a GOST title block — plus the placement scope (around an area or the whole drawing). No sibling tool does this, so an agent can distinguish it from draw_rectangle, add_table, or export_pdf without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage context: scale=0 means auto-fit, area is optional (falls back to the whole drawing), and it explicitly describes the follow-up step — "После него export_pdf без параметров печатает этот лист, export_pdf(all_sheets=True) все листы чертежа одним PDF" — routing the agent to the correct export variant. There is no explicit when-not-to-use or prerequisite statement (e.g., whether a drawing must already exist, whether a sheet can be remade), so it stops short of a 5.

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