Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

circular_pattern

Repeat features around a rotation axis to create bolt circles, fan blades, or gear tooth blanks. Control count, total angle, and equal or fixed spacing.

Instructions

Circular pattern (patrón circular) — repeat features around an axis.

Standard autoparts use: bolt circles on flanges, fan blades, gear teeth blanks, dial markings. Always preceded by a create_reference_axis call to define the rotation axis.

Args: feature_names: Names of features to pattern. Pass exact names from get_active_part_info — e.g. ["Cortar-Extruir1"] for one hole. axis_name: Name of the axis to rotate around. Use the "Eje1"-style name returned by create_reference_axis. count: Total number of instances INCLUDING the original (>= 2). For 6 holes around a bolt circle, pass count=6. total_angle_deg: Total angular span in degrees. Default 360 (full circle, evenly distributed). Pass smaller values for partial arcs (e.g. 180 for a semicircle pattern, 90 for a quarter, 120 for three instances spread over a third turn). equal_spacing: When True (default), total_angle_deg is the total span and instances divide it equally. When False, it's interpreted as the angle BETWEEN consecutive instances — useful for "every 30 degrees, count=N" use cases. reverse: Flip rotation direction (clockwise vs counter-clockwise when viewing along the axis).

Returns the new pattern Feature with name (e.g. "CirPattern1").

Example — bolt circle of 6 evenly-spaced holes around an axis through a hole's center: eje = create_reference_axis("Cara<3>@Cortar-Extruir1") circular_pattern(["Cortar-Extruir2"], eje["name"], count=6)

Example — 3 ribs over the top half of a flange (180° arc, equal spacing): circular_pattern( ["Saliente-Extruir1"], "Eje1", count=3, total_angle_deg=180.0, )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
reverseNo
axis_nameYes
equal_spacingNo
feature_namesYes
total_angle_degNo
Behavior4/5

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

No annotations provided, so description carries full burden. It explains parameter behaviors (equal_spacing, reverse, total_angle_deg) and mentions the return value (a new Feature with name). It does not discuss side effects or destructive actions, but the tool is a pattern creation which is typically non-destructive.

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?

Well-structured with clear sections, bullet points for arguments, and examples. While verbose, every sentence adds value for a parameter-heavy tool. Could be slightly more concise, but overall effective.

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?

Given 6 parameters and no output schema, the description covers all parameters, explains the return value, and provides two complete examples. It also notes the prerequisite, making it fully actionable for an AI agent.

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

Parameters5/5

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

Schema coverage is 0%, but the description provides detailed semantics for all 6 parameters, including types, defaults, and usage (e.g., count includes original, total_angle_deg default 360, equal_spacing behavior). This adds significant value beyond the bare schema.

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 'repeat features around an axis' and provides specific use cases like bolt circles and fan blades. It distinguishes from siblings like linear_pattern by describing the circular axis-based repetition and the prerequisite create_reference_axis call.

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?

The description explicitly mentions the prerequisite create_reference_axis call and provides examples for common use cases. It does not explicitly state when not to use, but the context and examples imply appropriate scenarios, and it guides the user on parameter settings for partial arcs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server