Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_polygon

Draws a regular polygon inscribed in a circle with a specified diameter in a SolidWorks sketch, using sides plus optional center and rotation to place the geometry.

Instructions

Draws a regular polygon (e.g. hexagon: sides=6) inscribed in a circle of the given diameter (mm): the vertices lie on the circle (for a hexagon, the diameter is the distance across corners).

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": {
      "sides": "<sides>",
      "circumscribed_diameter_mm": "<circumscribed_diameter_mm>"
    },
    "name": "sketch_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidesYesNumber of sides (>= 3)
center_x_mmNo
center_y_mmNo
rotation_degNo
circumscribed_diameter_mmYesDiameter in mm of the circle through the vertices

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / circumscribed_diameter_mm / description
      Previous value: -"Inscribed circle diameter in mm"New value: +"Diameter in mm of the circle through the vertices"
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's main added value is the geometric contract – the circumscribed circle through the vertices. It says nothing about which sketch geometry is added to, whether an active sketch is required, or that repeated calls create separate polygons, leaving real behavioral gaps for a mutation tool.

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 a parenthetical example that earns its place by disambiguating the diameter convention. No filler, though the example could be trimmed slightly without loss.

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?

With an output schema present there is no need to describe return values, and the description covers the geometry contract well for a 5-parameter draw operation. The remaining gap – no mention of the active sketch or existing geometry the polygon is added to – is the main reason it is not a 5.

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 only 40%, and the description genuinely adds meaning for circumscribed_diameter_mm ("distance across corners"), which resolves the inscribed-vs-circumscribed ambiguity that the schema name alone leaves open. However, center_x_mm, center_y_mm and rotation_deg are undocumented in both schema and description, so it only partially compensates for the coverage gap.

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 and resource ("Draws a regular polygon") and pins down the geometric meaning of the driving parameter (vertices lie on the circle; for a hexagon the diameter is the distance across corners). It does not explicitly contrast itself with siblings such as sketch_circle or sketch_line, but the resource is unambiguous enough that an agent can select it without confusion.

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?

Usage is only implied: an agent can infer this is the tool for creating a regular n-gon in a sketch. There is no statement of when to prefer it over sketch_circle plus patterns, or of prerequisites such as needing an active sketch, so guidance is minimal but not misleading.

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