Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

set_layer

Configure or create an AutoCAD layer and set its visibility, freeze, lock, color, linetype, lineweight, and current status in one call.

Instructions

Настроить слой (создаётся, если нет): on (вкл/выкл), frozen, locked, color (ACI), linetype (DASHED, CENTER, HIDDEN...: подгружается сам), lineweight (мм, напр. 0.5), current=True: сделать текущим.

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

Input Schema

NameRequiredDescriptionDefault
onNo
nameYes
colorNo
frozenNo
lockedNo
currentNo
linetypeNo
lineweightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two real traits: the layer is created if absent, and linetypes are loaded automatically rather than needing to pre-exist. It stays silent on permissions, whether unspecified properties are reset or left untouched, and whether current=True changes other layers' current status.

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?

One dense sentence that front-loads the action and the create-if-missing caveat, then walks the parameters. The telegraphic style is efficient, though the heavy parenthetical nesting makes it slightly harder to scan than a short bulleted form.

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?

For an 8-parameter mutation tool with no annotations, the parameter-level coverage is decent and an output schema exists so return values need no explanation. The gaps are behavioral: no statement about partial-update semantics or side effects on other layers when current=True, which an agent needs before mutating drawing state.

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 it largely does: it explains that color is an ACI index, that linetype takes names like DASHED/CENTER/HIDDEN, that lineweight is in millimeters with an example value, and that current=True makes the layer current. Only the required name parameter is left implicit, which is reasonable.

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 opens with a specific verb+resource ("Настроить слой") and adds the key scope detail that the layer is created when missing, so the agent knows this is an upsert rather than a pure edit. It does not, however, contrast itself with the sibling create_layer, even though the auto-creation behavior overlaps with it.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: nothing says when to call set_layer instead of create_layer or set_properties, nor whether existing unlisted properties are preserved. Usage must be inferred entirely from the parameter list.

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