Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sketch_circular_pattern

Create circular patterns of sketch entities centered on the sketch origin. Essential for bolt circles, gear teeth, and radially symmetric features.

Instructions

Create a circular pattern of sketch entities around the sketch origin.

Generates a circular array of selected sketch entities. The rotation axis is always the sketch origin — SOLIDWORKS' CreateCircularSketchStepAndRepeat does not expose a pattern-centre parameter. Position the seed entity at the desired radius from the origin; the pattern derives its radius from the seed's centre.

Essential for creating bolt circles, gear teeth, and other radially symmetric features around the sketch origin.

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_dataYesThe input data value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Discloses key behavior: rotation axis is sketch origin, radius derived from seed entity. With no annotations, description carries burden. However, it does not explain how input_data should be structured or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs, first sentence defines core purpose. Technical details follow without redundancy. No unnecessary words or vague statements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides enough context for basic usage but omits details about expected input structure (e.g., entity selection, instance count, angle). Given the tool has an output schema, return values are covered. However, the parameter ambiguity weakens completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'input_data' has a minimal schema description ('The input data value.'). The tool description adds no further meaning about what should be provided, leaving the agent uncertain about required fields.

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?

The description clearly states it creates a circular pattern of sketch entities around the sketch origin. It distinguishes from siblings like 'sketch_linear_pattern' by specifying the circular nature and the center being the origin.

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?

Provides explicit usage scenarios like bolt circles and gear teeth. Mentions the limitation that the center is fixed at the sketch origin, implying not to use when a different center is needed. Lacks explicit alternatives or when-not conditions.

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