Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_polygon

Adds a regular polygon with corners on a construction circle from center, radius, and side count. Dimension the circle to resize it; returns side-line and circle IDs.

Instructions

Add a regular polygon whose corners lie on a circle of the given radius; the first corner is at angle 0. It is made of lines tied to a construction circle, so dimension that circle to resize the polygon; in a part that diameter becomes a dimension when the sketch is closed, unless set first. Returns line_ids (the sides, in order) and circle_id, the ids list_sketch_entities shows.

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": {
      "cx": "<cx>",
      "cy": "<cy>",
      "radius": "<radius>",
      "sides": "<sides>"
    },
    "name": "draw_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
cxYesX of the centre
cyYesY of the centre
unitNomm, cm, m, inch or ft
sidesYesHow many sides, 3 to 100
radiusYesRadius of the circle the corners lie on

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 supplied, the description carries the full burden and does substantial work: it discloses that sides are lines tied to a construction circle, that resizing is done through that circle, the part/sketch-closing behavior of the diameter dimension, and the exact return shape (line_ids in order plus circle_id). It omits prerequisites and failure modes, but the disclosure well beyond the bare operation is unusually strong.

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?

Two dense sentences, front-loaded with the operation and geometry before the construction/dimension caveat and the return values. Nothing is redundant, though 'unless set first' is compressed enough to be slightly ambiguous on a first read.

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 five-parameter mutation tool with no annotations and no output schema, the description covers the return payload and the non-obvious downstream behavior of the construction circle, which is exactly the kind of thing an agent cannot infer. It stops short of stating required preconditions such as an open sketch or the unit default, leaving a small completeness gap.

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 the baseline is 3, and the description adds meaning the schema does not: the angle-0 orientation of the first corner explains how cx, cy, and sides jointly place the polygon, and the return-value note ties radius to a durable construction circle. That is genuine semantics on top of already-complete parameter docs.

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 (add) and resource (regular polygon) and pins down the exact construction semantics: corners lie on a circle of the given radius with the first corner at angle 0. That geometry makes it unmistakable versus siblings like draw_circle, draw_polyline, or draw_rectangle without needing to open their schemas.

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

Usage Guidelines3/5

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

Gives real how-to-use guidance (dimension the construction circle to resize the polygon, and how that diameter behaves when the sketch is closed), but says nothing about when to pick this over draw_polyline or draw_rectangle. Usage is implied by the geometry rather than stated, and no exclusions or prerequisites (e.g., an active sketch) are named.

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