Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_polyline

Create a connected chain of sketch lines through ordered points in one call, optionally closing the loop, instead of drawing each segment separately.

Instructions

Add a chain of lines through the points given, in one call (instead of one draw_line per side): each point joins the next, and closed: true also joins the last to the first, so an outline such as an L profile is one call. Exact coordinates, no snapping; lines along x or y get horizontal / vertical relations. In a part, a two-point polyline (one line) that touches nothing when the sketch is closed gets its length as a dimension, as with draw_line. Returns the new entity ids in order.

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
unitNomm, cm, m, inch or ft
closedNotrue joins the last point back to the first (a closed outline)
pointsYesThe corners in order, e.g. [{'x': 0, 'y': 0}, {'x': 80, 'y': 0}, {'x': 80, 'y': 6}]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: no snapping, automatic horizontal/vertical relations, an auto-dimension applied to untouched two-point polylines in a part, and the return value (new entity ids in order). The one notable omission is a precondition — whether an active sketch is required to call it.

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?

The key differentiator (one call instead of many draw_line calls) is front-loaded and the sentences carry real information with no filler. The dimensioning clause is a bit dense and arrives late, but it is not padding.

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?

For a three-parameter geometry tool with no output schema, the description covers creation semantics, side effects, and the return value, which is nearly everything an agent needs. Only the sketch-context precondition is left implicit.

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 coverage is 100%, so points, closed, and unit are already documented structurally. The description reinforces ordering semantics ("each point joins the next") and the closed-loop effect, but adds no unit syntax or format detail beyond the schema, so the baseline applies.

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?

"Add a chain of lines through the points given, in one call" names a specific verb (add) and resource (chained lines) and immediately frames the scope difference from draw_line ("instead of one draw_line per side"). An agent can tell this apart from draw_line without opening either schema.

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

Usage Guidelines4/5

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

It explicitly routes the agent away from the per-side alternative (draw_line) and gives a concrete use case (an L profile outline in one call). It does not address when to prefer draw_polygon for a closed outline, so the guidance is clear but not exhaustive.

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