Skip to main content
Glama

Polar Pattern

polar_pattern

Repeats a PartDesign feature around X, Y, Z, or a selected edge using a set angle and occurrence count to create circular patterns.

Instructions

Repeat a PartDesign feature around an axis.

axis: 'X'|'Y'|'Z' for body origin axes, or {handle, edge: tag|'EdgeN'}. angle_deg: total swept angle (default 360 = full circle). occurrences: number of copies (>=2). Includes the original.

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": {
      "feature": "<feature>"
    },
    "name": "polar_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNoZ
nameNoPolarPattern
featureYes
reversedNo
angle_degNo
workspaceNoRun this call in this named workspace
occurrencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the description's main added value is the note that occurrences include the original copy, which is genuinely useful. It does not say whether a new pattern feature is inserted into the tree, what happens to the source feature, or whether the call requires a prior transaction.

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?

The core action is front-loaded in one sentence, followed by terse per-parameter clarifications with no filler. Every line contributes semantics an agent cannot get from the schema.

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

Completeness3/5

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

For a mutation tool with no output schema and no readOnly safety net, the description covers the geometry semantics well but omits what the call returns, whether it modifies the feature tree, and the meaning of 'reversed'. Adequate to invoke, not quite complete.

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

Parameters4/5

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

With only 14% schema coverage, the description carries real weight and does so for three parameters: the axis accepts 'X'|'Y'|'Z' or a {handle, edge} object, angle_deg is the total swept angle with 360 meaning a full circle, and occurrences must be >=2. It leaves 'name', 'reversed' and the required 'feature' parameter unaddressed.

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 a PartDesign feature around an axis'), which is precise enough to separate it from the linear-pattern sibling. It never names linear_pattern or mirrored explicitly, so the differentiation is inferred from 'around an axis' 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 only implied by the operation itself; there is no statement of when to prefer this over linear_pattern or mirrored, and no prerequisite such as needing an existing body/feature or an open transaction. The angle/occurrence defaults hint at typical use but do not guide selection.

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