Power CAD MCP

by khs0927

Overview Schema Source Related Servers Discussions Admin

Hybrid

set_entity_properties

Change an entity's layer, color, linetype, or lineweight to control drawing appearance and organization.

Instructions

Change an entity's layer, color, linetype or lineweight.

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": {
      "handle": "<handle>"
    },
    "name": "set_entity_properties"
  }
}

Input Schema

Name	Required	Description
`color`	No	ACI 0-256 or name (red, yellow, green, cyan, blue, magenta, white, bylayer)
`layer`	No	Target layer (created if missing). Default: current layer.
`handle`	Yes
`linetype`	No	Linetype name, e.g. CONTINUOUS, DASHED, CENTER, HIDDEN
`lineweight`	No	1/100 mm; -1 ByLayer

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare a mutating (readOnlyHint=false), non-destructive, non-idempotent operation, and the description's 'Change' aligns with that. It adds no context beyond the annotations, such as reversibility of the edit or that the target is identified by handle. With annotations covering the safety profile, a 3 is appropriate.

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?

A single front-loaded sentence with zero waste; the changed properties are listed immediately. It is efficient, though it stops short of any additional useful scoping.

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, and annotations cover safety. However, for a 5-parameter mutation tool the description omits the required handle as the targeting key and offers no behavioral detail, leaving it minimally adequate rather than complete.

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 high (80%), so the schema already documents ACI codes, layer auto-creation, linetype names, and lineweight units. The description only restates the four editable properties and adds no format or syntax detail beyond the schema, matching the baseline for high coverage.

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?

Names a specific verb ('Change') and resource ('an entity's') plus the exact editable properties (layer, color, linetype, lineweight), which separates it from geometry/transform siblings like move_entities or rotate_entities. It does not explicitly name the sibling it complements, but the field list makes the scope unambiguous.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives (e.g., use move_entities for geometry instead). Usage is only implied by the stated purpose.

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