Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

create_layer

Creates an AutoCAD layer by name or updates an existing layer's ACI color (1–255) for organized, color-coded drawings.

Instructions

Создать слой или поменять цвет существующего: имя и цвет AutoCAD (ACI 1..255). Рисование на слое цвет не сбрасывает.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo

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?

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by stating the ACI color domain (1..255) and by clarifying that drawing on a layer does not reset its color, but it omits permissions, case sensitivity, uniqueness of names, and the effect of passing an existing name — meaningful gaps for a mutation tool with zero annotation coverage.

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?

A single sentence front-loads the primary action (create a layer) before the secondary one (recolor), and the trailing note about drawing not resetting the color is compact and useful. No filler or redundancy.

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 values need not be described. However, for an unannotated mutation tool the description should still clarify the create-vs-update branch (what happens if the name already exists) and the name's constraints; the color side is well covered, the name side is not.

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 description coverage is 0% for two parameters, so the description must compensate. It explains the color parameter well by giving the ACI 1..255 range and tying it to AutoCAD, but it says nothing about the required name parameter beyond the word "имя" — no format, uniqueness, or matching rules — leaving half the parameters under-specified.

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 concrete verb and resource ("Создать слой") and adds a second capability ("поменять цвет существующего"), so an agent knows it both creates and recolors. It does not explicitly contrast with siblings like set_layer or delete_layer, but the dual create-or-modify scope 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?

Usage is only implied by the stated purpose: call it to create a layer or to change a layer's color. There is no explicit when-not guidance, no mention of set_layer as the alternative for other layer properties, and no prerequisite information such as whether the layer must already exist or what happens on a name collision.

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