Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

set_properties

Modify AutoCAD object properties—layer, color, linetype, lineweight, and linetype scale—for selected handles or entities filtered by layer, type, or area.

Instructions

Сменить свойства объектов (handles или фильтр filter_layer/entity_type/area): layer (перенести на слой), color (ACI, 256 = по слою), linetype (DASHED, CENTER...), lineweight (мм; -1 по слою), ltscale: масштаб типа линии (для 1:100 обычно 100, иначе штрихи сливаются).

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

Input Schema

NameRequiredDescriptionDefault
areaNo
colorNo
layerNo
handlesNo
ltscaleNo
linetypeNo
lineweightNo
entity_typeNo
filter_layerNo

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 burden; it does disclose real behavioral detail (ACI 256 = ByLayer, lineweight -1 = ByLayer, ltscale ~100 for 1:100 to avoid merged dashes). What it omits is mutation-relevant context: whether the target layer must already exist, whether changes are reversible, and what happens on unresolvable handles. For a write tool with zero annotation coverage, that gap keeps it at 3.

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 front-loaded sentence with the action first, then the selection mechanism, then per-property glosses — no filler. It is dense and reads as a run-on, but every clause supplies distinct information, so 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 values need not be explained, but this is a 9-parameter mutation tool with no annotations and the description says nothing about preconditions or failure modes (nonexistent layer, unmatched handles, empty filter). It is complete enough to call correctly in the happy path but thin for a destructive operation.

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?

With 0% schema description coverage across 9 parameters, the description has to compensate almost entirely, and it largely does — it maps color, layer, linetype, lineweight, and ltscale to concrete value conventions and units (ACI index, millimetres, sentinel -1/256), plus covers handles, filter_layer, entity_type, and area as selectors. Remaining ambiguity: 'area' is only named, not defined (the schema shows a bare number array with no hint that it is a bounding box), and the handle string format is unspecified.

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?

States a specific verb+resource ("Сменить свойства объектов") and immediately enumerates which properties are mutable (layer, color, linetype, lineweight, ltscale) plus the two selection modes (handles or filter). An agent can tell this acts on entities, unlike the similarly named set_layer which configures the layer table. It never names a sibling alternative explicitly, so it stops just short of full differentiation.

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?

The description reveals the two targeting strategies — explicit handles versus a filter of filter_layer/entity_type/area — which is genuine how-to-use guidance. However, it gives no when-to-use versus when-not guidance, no statement that at least one selection input is needed, and no alternatives named. Usage is implied rather than prescribed.

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