Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_set_properties

Update one CAD object's layer, color, linetype, or visibility while leaving other properties unchanged; use it to style entities, not to move, rotate, or scale them.

Instructions

Update selected properties of one object—layer, color, linetype, or visibility—while leaving unspecified properties unchanged.

Side-effects: Modifies entity visual properties. Disambiguation: Use to style entities; for spatial changes use object_move, object_rotate, or object_scale.

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": {
      "object_id": "<object_id>"
    },
    "name": "object_set_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoAutoCAD Color Index (ACI 0-256; 0=ByBlock, 256=ByLayer)
layerNoTarget layer name. Layer must exist
visibleNoEntity visibility flag (True=visible, False=hidden)
linetypeNoLinetype name to assign (e.g. 'Continuous', 'DASHED')
object_idYesBackend entity identifier or persistent CAD handle

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / color / description
      Added value: +"AutoCAD Color Index (ACI 0-256; 0=ByBlock, 256=ByLayer)"
    • addedInput schema / properties / layer / description
      Added value: +"Target layer name. Layer must exist"
    • addedInput schema / properties / linetype / description
      Added value: +"Linetype name to assign (e.g. 'Continuous', 'DASHED')"
    • addedInput schema / properties / object_id / description
      Added value: +"Backend entity identifier or persistent CAD handle"
    • addedInput schema / properties / visible / description
      Added value: +"Entity visibility flag (True=visible, False=hidden)"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, and the description adds a real behavioral fact beyond that: 'Side-effects: Modifies entity visual properties' plus the partial-update guarantee that unspecified properties are left unchanged. It does not cover persistence (whether a save/transaction is needed) or failure modes, so it stops short of full disclosure.

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?

Three short, labeled lines (main behavior, Side-effects, Disambiguation) with the primary action front-loaded. No filler and nothing redundant with the schema.

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?

With an output schema present, return values need no explanation, and the description covers mutation scope and sub-tool routing. It leaves out whether a transaction/commit is required for changes to persist and what error surfaces when a layer name doesn't exist.

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 100%, so baseline is 3, but the description adds semantics the schema lacks: that omitted/null properties are left unchanged rather than reset. It still doesn't explain the null-vs-omitted distinction per parameter or ACI/linetype validity rules, which stay in the schema.

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?

States a specific verb and resource ('Update selected properties of one object') and enumerates the exact property set (layer, color, linetype, visibility). It also distinguishes itself from spatial siblings in the same breath, so an agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Use to style entities; for spatial changes use object_move, object_rotate, or object_scale.' That names both the condition for this tool and the concrete alternatives for the excluded case.

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

Deploy Server

Other Tools