Power CAD MCP

Overview Schema Source Related Servers Discussions Admin

draw_line

Create a straight line segment by specifying start and end coordinates, with optional color, layer, and linetype, to add precise geometry to CAD drawings.

Instructions

Draw a straight line segment.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "draw_line"
  }
}

Input Schema

Name	Required	Description
`end`	Yes	[x, y] or [x, y, z]
`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.
`start`	Yes	[x, y] or [x, y, z]
`linetype`	No	Linetype name, e.g. CONTINUOUS, DASHED, CENTER, HIDDEN

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare the safety profile (not read-only, non-destructive, non-idempotent), so the bar is lower, but the description adds nothing beyond them. It omits relevant behavior such as the default layer, coordinate expectations (2D vs 3D), or that a missing layer gets created (only stated in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste, but it is under-specified for a 5-parameter CAD drawing operation rather than genuinely well-sized. Brevity here reads as thinness more than economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and annotations exist, so return values need not be explained, but the description fails to cover drawing context an agent needs: target layer defaults, coordinate system/units, and how it differs from sibling drawing tools. Given the crowded sibling set, this leaves real gaps.

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 100% (start/end coordinate format, color ACI/name options, layer creation behavior, linetype names), so the schema carries the meaning. The description contributes no additional parameter insight, making the baseline 3 appropriate.

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 ('Draw') and resource ('straight line segment'), which is unambiguous about the resulting entity. However, it does not distinguish itself from nearby siblings like draw_polyline or the line-producing variants, leaving sibling selection to 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 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 and no mention of alternatives such as draw_polyline for multi-segment geometry. The agent must infer from the name alone that this is the right tool for a single segment.

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