Skip to main content
Glama
hedless

Onshape MCP Server

by hedless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_circular_pattern

Create a circular pattern of selected features around a specified axis, with control over angle, count, and reapplication of features for reliable results.

Instructions

Create a circular pattern of features around an axis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisNoPattern axisZ
nameNoPattern nameCircular pattern
angleNoTotal angle spread in degrees
countYesTotal number of instances
elementIdYesPart Studio element ID
documentIdYesDocument ID
featureIdsYesFeature IDs to pattern
workspaceIdYesWorkspace ID
reapplyFeaturesNoRe-run the patterned features per instance (Onshape's 'Reapply features'). Turn on if the pattern fails with PATTERN_SWITCH_TO_PER_INSTANCE because the patterned body was later filleted, chamfered or booleaned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / reapplyFeatures
      Added value: +{
+  "default": false,
+  "description": "Re-run the patterned features per instance (Onshape's 'Reapply features'). Turn on if the pattern fails with PATTERN_SWITCH_TO_PER_INSTANCE because the patterned body was later filleted, chamfered or booleaned",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action “Create”, but does not mention that this modifies the document, what permissions are needed, whether it can fail, or what side effects may occur. This is minimal disclosure for a mutating CAD operation.

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?

The description is a single, clear sentence with no filler or redundant information. It is front-loaded with the core purpose, though it sacrifices substantive detail, which is a conciseness tradeoff rather than a structural flaw.

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

Completeness2/5

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

This is a complex create operation with 9 parameters, 5 required, no output schema, and no annotations. The one-line description does not explain return semantics, example usage, failure modes, or the relationship of parameters such as axis, angle, count, and reapplyFeatures. The description alone is insufficient for an agent to reliably invoke this tool.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds no additional parameter detail beyond the schema, but does not need to because each parameter already has a meaningful schema description.

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 states a clear verb and resource: “Create a circular pattern of features around an axis”. The word “circular” distinguishes it from the sibling create_linear_pattern, and “features” indicates what is patterned, so an agent can identify the tool's function without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus create_linear_pattern or other cad operations. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage from the name alone.

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