Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_polyline

Draw a polyline from coordinate points, optionally closing the contour or assigning a layer to create connected geometry in AutoCAD drawings.

Instructions

Полилиния по точкам [[x,y],...]. closed: замкнуть контур.

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": {
      "points": "<points>"
    },
    "name": "draw_polyline"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo0
closedNo
pointsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about coordinate system, units, whether a new entity is appended or an existing one modified, or any failure conditions for malformed point lists. The only disclosed behavior is that closed=true joins the contour; the existence of an output schema covers the return value, but the mutation profile remains undisclosed.

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?

Two short clauses, front-loaded with the core resource and its input shape, with zero filler. However, the brevity crosses into telegraphic under-specification, and the mixed Russian/English wording adds friction without adding precision.

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?

For a write tool with three parameters, no annotations, and no schema descriptions, the definition leaves the layer target, coordinate conventions, and any side effects unaddressed. The output schema relieves it of describing return values, but the input-side gaps are too large for the tool's complexity.

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 0%, so the description must compensate, and it partially does: it specifies the points format as a list of [x,y] pairs and explains that closed closes the contour. The layer parameter (default "0") is never mentioned, leaving a third of the inputs documented only by a bare type and default.

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 identifies the resource (a polyline) and its construction input (a list of [x,y] points), plus the effect of the closed flag, so an agent can tell it draws a multi-vertex connected path rather than a single segment. It never explicitly contrasts itself with draw_line, draw_polygon, or draw_spline, and the drawing verb is only implied by the noun phrase.

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 statement of when to choose a polyline over draw_line, draw_polygon, or draw_spline, and no mention of prerequisites such as an active drawing or layer. The agent must infer usage entirely from the name and the point-list format.

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