Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_circular_pattern

Repeats sketch entities in an open sketch around a center to create circular patterns, such as bolt holes on a flange, with count, angle, rotation, and center controls.

Instructions

Repeats sketch entities of the open sketch around a centre (e.g. bolt holes on a flange before one cut). entity_points: [[x, y], ...] one point on each entity; the copies are spread evenly over angle_deg around (center_x_mm, center_y_mm). The entities' centre is computed (for a circle: its centre); give reference_x_mm / reference_y_mm to set it explicitly. rotate=False keeps the copies' orientation. Replaces the selection.

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": {
      "entity_points": "<entity_points>",
      "count": "<count>"
    },
    "name": "sketch_circular_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesInstances, original included (>= 2)
rotateNo
angle_degNoTotal angle in degrees
center_x_mmNo
center_y_mmNo
entity_pointsYes
reference_x_mmNo
reference_y_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare mutation with idempotentHint=false but non-destructive, and the description adds real behavioural detail beyond that: how the pattern centre is derived (circle centre) and how to override it, that rotate=False preserves orientation, and that the current selection is replaced. The 'Replaces the selection' note is the kind of side effect an agent needs, and it does not conflict with destructiveHint=false since no geometry is destroyed.

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?

Purpose is front-loaded in the first clause and the remaining text is dense with parameter meaning rather than filler. Sentences are long and run together (entity_points, spread, centre override, rotate, selection replacement all in one block), which slightly hurts scannability but no sentence is wasted.

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 non-destructive mutation tool with an output schema and full annotation coverage, the description supplies the essential mechanics: what gets patterned, how the centre is chosen, orientation handling, and the selection side effect. Minor omissions remain, such as how angle_deg=360 combined with count closes the loop and any failure cases (e.g., entities without a computable centre).

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 description coverage is only 25% across 8 parameters, so the description has to compensate and largely does: it defines the entity_points format ('[[x, y], ...] one point on each entity'), explains how angle_deg spreads copies, identifies center_x_mm/center_y_mm as the rotation centre, and explains reference_x_mm/reference_y_mm and rotate=False. Only count and the interaction between angle_deg=360 and count are left to the schema alone.

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?

Names a specific verb and resource ('Repeats sketch entities of the open sketch around a centre') plus a concrete example ('bolt holes on a flange'), which pins down the operation precisely. The 'sketch' qualifier implicitly separates it from the feature-level circular_pattern and from sketch_linear_pattern, but no sibling is named explicitly.

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?

The flange/bolt-hole example conveys the intended usage context, so the when-to-use case is implied rather than stated. There is no explicit guidance on when to prefer the feature-level circular_pattern or sketch_linear_pattern instead, and no stated prerequisites such as needing an active sketch.

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