Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

circular_pattern

Creates circular patterns of selected SOLIDWORKS features around a model axis or cylindrical face/circular edge, spreading instances evenly over 360 degrees or at a fixed angle.

Instructions

Pattern one or more features around a model axis through the origin (x, y or z), or around the axis of a cylindrical face or circular edge (axis_point). count includes the original. Instances are spread evenly over 360 degrees by default; angle_between sets a fixed step instead.

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

Input Schema

NameRequiredDescriptionDefault
axisNoModel axis through the origin
flipNoGo round the other way
unitNoUnit for axis_point (mm, cm, m, inch or ft)
countYesInstances including the original
featuresNoFeature names from list_features. Default: the last solid feature.
axis_pointNo
angle_betweenNoDegrees between neighbouring instances (default: evenly over 360)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does useful work here: count includes the original, spacing defaults to even over 360 degrees, angle_between overrides that default, flip reverses direction, and features defaults to the last solid feature. What it omits is the mutation profile — whether new bodies/instances are created, whether the operation is reversible, and what the call returns — which matters for an unannotated modeling operation.

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?

Three tight sentences, front-loaded with the core action and resource, then the two axis modes, then the counting and spacing rules. No filler or repetition.

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 seven-parameter mutation tool with no output schema and no annotations, the description covers the essential calling semantics: how to specify the axis two different ways, what count means, and how spacing is determined by default or by angle_between. The remaining gap is that it says nothing about the effect on the model or the failure modes, which is a meaningful but not fatal omission.

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 86%, so the baseline is 3. The description adds real meaning for axis_point — tying it to the axis of a cylindrical face or circular edge, which the schema itself leaves undocumented — and reinforces the count and angle_between defaults. Most other parameters are already self-documenting in the schema, so the net gain is modest.

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?

The description opens with a specific verb and resource ("Pattern one or more features") and immediately constrains the geometry to rotation about an axis, which separates it in practice from a linear pattern. It stops short of naming linear_pattern as the alternative, so the differentiation is inferred from geometry rather than stated.

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 implied by the two axis modes described (origin axis vs. cylindrical face/circular edge axis), which tells an agent which parameters to reach for. There is no explicit when-to-use / when-not guidance and no mention of linear_pattern as the alternative for straight-line patterning, nor any prerequisites such as an open document or selected features.

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