Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Circular Pattern

pattern_circular

Repeats selected features around a named axis to create circular arrays such as rings of bosses, ribs, or holes; specify count, angle, and spacing for the pattern.

Instructions

Repeat features of the active part around an axis, e.g. a ring of bosses or ribs.

Create the axis first with create_axis. Bosses and cuts both work (a ring of holes is a patterned cut). It fails when the volume doesn't change, which means no instance landed on the part. Needs: an open part with the named features and axis. Changes: adds a circular pattern feature. Returns: pattern with name, patterned, axis, count, angle, equal_spacing, and volume_before, volume_after and volume_change (mm³, negative for cuts).

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": "pattern_circular"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe pattern. `features` (at least one), `axis` and `count` (2 or more, the original included) are required; `angle` (360) and `equal_spacing` (on) have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare it as a non-readonly, non-idempotent, non-destructive write; the description adds the preconditions (open part with the named features and axis), the exact mutation ('adds a circular pattern feature'), and a diagnosis for the failure mode. That is well beyond what the annotations provide and tells the agent what state it needs and what it will change.

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 purpose in one sentence, then uses compact labeled fragments (Needs/Changes/Returns) that are easy to scan. A few items (count >= 2, angle default) duplicate the schema, keeping it just short of maximally concise.

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

Completeness5/5

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

For a feature-mutating tool with nested parameters, the description covers prerequisites, what is modified, the failure condition, and return shape, including that volume_change is negative for cuts. An agent has everything needed to call it correctly and interpret the outcome.

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 nested object description already documents `features`, `axis`, `count` defaults and constraints, so the schema carries the parameter burden. The description only echoes `axis`, `count`, and `angle` in the return-value sentence and adds no new parameter meaning, making the baseline 3 appropriate.

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 ('repeat features of the active part around an axis') plus a concrete example ('a ring of bosses or ribs'). It implicitly separates itself from the sketch-level siblings by scoping to features of the active part, but it never names `sketch_circular_pattern`, so an agent must infer the distinction.

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 real prerequisite ('Create the axis first with `create_axis`'), clarifies that both bosses and cuts are valid inputs, and describes the failure case ('fails when the volume doesn't change'). It stops short of explicitly saying when to prefer it over the sibling `sketch_circular_pattern`, so usage is clear but not fully routed.

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