Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Sketch Circular Pattern

sketch_circular_pattern

Repeat selected sketch entities around the sketch origin to create bolt circles or radial patterns, then cut once with an extrusion.

Instructions

Repeat sketch entities around the sketch origin, e.g. a bolt circle.

The centre is always the sketch origin, so draw the first entity at the radius you want from it. Then cut once with create_cut_extrude. Needs: an open sketch (create_sketch). Changes: adds copies of the entities. Returns: pattern with id, entities, count and angle.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesA mapping: `entities` (ids to repeat), `count` (instances, default 6) and `angle` (degrees spread over, default 360).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Adds real context beyond the annotations: the pivot is always the sketch origin, the sketch must be open, and the operation adds copies rather than modifying the source, which is consistent with destructiveHint=false. It does not describe failure modes (e.g. oversized count/radius) or interaction with existing geometry, which the annotations alone don't cover. Solid but not rich.

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?

Front-loads the core action, then uses labelled Needs/Changes/Returns blocks for fast scanning; minimal waste. The trailing Returns sentence largely restates the output schema, a small redundancy in an otherwise tight definition.

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?

Covers precondition, pivot behaviour, side effects and downstream step, which is more than most pattern tools offer. Since an output schema exists, the return-value sentence is optional, and no pagination or error behaviour is needed for this local-geometry operation. An agent has everything required to call it correctly.

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% and the schema already documents entities, count and angle with defaults, so the baseline is 3. The description does add one useful insight — the entity's drawn position sets the pattern radius, since the centre is fixed at the origin — but does not explain the angle/count interaction beyond the schema.

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 and resource ('Repeat sketch entities around the sketch origin') plus a concrete example ('a bolt circle'). The phrase 'sketch entities' and the open-sketch requirement distinguish it from the feature-level sibling pattern_circular without needing to name it.

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?

Gives a clear workflow: draw the first entity at the target radius, run this, then cut once with `create_cut_extrude`. It also states the precondition (an open sketch via `create_sketch`). It stops short of explicitly naming when NOT to use it versus pattern_circular, so not a 5.

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