Skip to main content
Glama
solidworks-mcp

solidworks-mcp

circular_pattern

Repeats selected features around a model or edge axis, placing a specified number of copies evenly across a total angle. Use it to build radial feature arrays in SolidWorks parts.

Instructions

Repeats features (names from get_feature_tree) around an axis: count copies in total (original included), spread evenly over angle_deg. axis: a model axis through the origin, or "edge" to turn around the circular or straight edge through axis_edge_point ([x, y, z] in mm, e.g. on the rim of a central hole). The first use of a model axis adds a hidden reference axis "Axis Z (MCP)" (X, Y) to the tree.

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

Input Schema

NameRequiredDescriptionDefault
axisNoz
countYesNumber of copies (including original, >= 2)
reverseNo
featuresYes
angle_degNoTotal angle in degrees (0 < angle <= 360)
axis_edge_pointNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the generic profile (non-read-only, non-idempotent, non-destructive, closed-world). The description adds real behavioral context beyond them: that count includes the original, that copies spread evenly across angle_deg, and that the first model-axis use silently injects a hidden 'Axis Z (MCP)' reference axis into the feature tree. It leaves unclear whether the original feature is moved or preserved and what errors look like, keeping it below 5.

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?

It is front-loaded with the core action and count semantics, then the axis mode, then the side-effect note — a sensible ordering with no filler. The telegraphic line-broken phrasing around 'axis:' is slightly terse but readable.

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?

An output schema exists, so return values need not be described, and the description covers geometry semantics plus the hidden-axis side effect for this 6-parameter mutation tool. The only substantive gaps are the undocumented 'reverse' flag and the axis default, which keep it from being fully complete.

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 description coverage is only 33%, and the description does compensate substantially: it defines count (total, original included), angle_deg (even spread), axis (model axis or 'edge'), and axis_edge_point ('[x,y,z] in mm, e.g. on the rim of a central hole'). However 'reverse' is never explained and the axis enum values x/y/z with default z are left to the schema, so meaning is added but not complete.

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 leads with a specific verb and resource ('Repeats features ... around an axis'), which inherently separates it from linear_pattern, and it names get_feature_tree as the source of valid feature names. It does not address the closely named sibling sketch_circular_pattern (features vs. sketch entities), so an agent must infer that boundary.

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?

It gives a useful prerequisite by pointing to get_feature_tree for feature names, and explains the 'edge' mode versus a model axis. It never states when to choose this over linear_pattern or sketch_circular_pattern, and no failure conditions are mentioned, so routing guidance is only implied.

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