Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

add_rectangular_pattern

Creates a row or grid pattern of selected features, including sheet-metal cuts, by setting counts, spacing, and axes.

Instructions

Repeat features in a row or a grid — a line of slots, a field of mounting holes, louvres. One hole + add_rectangular_pattern instead of twenty holes: one number changes the pitch. Works on sheet metal cuts too. A pattern whose copies all miss the body is taken back.

Args: features: Feature indices or names, ","-separated (manage_features list), e.g. "3" or "Hole1,Cut2". x_count: Instances along x_axis, the original included. x_spacing: Pitch in mm along x_axis; negative = the other way. x_axis: X, Y or Z (model axes). y_count: Rows along y_axis (1 = a single row). y_spacing: Row pitch in mm; negative = the other way. y_axis: X, Y or Z, different from x_axis.

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>"
    },
    "name": "add_rectangular_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_axisNoX
y_axisNoY
x_countNo
y_countNo
featuresYes
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
x_spacingNo
y_spacingNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.2/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 burden. It does disclose one important behavior — a pattern whose copies all miss the body is rolled back — which tells the agent failures are clean rather than partial. But it omits whether the original feature is consumed or referenced, whether the operation is reversible, and any permission/model-state prerequisites for a mutation tool.

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?

Front-loaded with purpose, then rationale, then a caveat, then a parameter block — a sensible order with little waste. The Args section restates parameter names already in the schema, but each line adds information rather than repeating it, so the length is defensible.

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 an 8-parameter mutation tool with no annotations, the definition covers purpose, the key usage rationale, failure rollback, and all semantically ambiguous parameters; return values need not be described because an output schema exists. The main residual gap is the interaction between the original feature and its instances (referenced vs. consumed).

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 only 13% (just the 'instance' param), and the description compensates well: it explains that x_count includes the original instance, that negative spacing reverses direction, that y_axis must differ from x_axis, that y_count=1 means a single row, and that features are comma-separated indices or names sourced from manage_features. These are semantics the schema's bare types and defaults do not convey.

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?

States a specific verb+resource ('Repeat features in a row or a grid') and immediately grounds it with concrete examples (slot lines, mounting-hole fields, louvres). The word 'rectangular' plus the axis-based parameters make it distinguishable from add_circular_pattern and add_mirror 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 Guidelines4/5

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

Gives clear usage guidance in the form of a design-intent recommendation: 'One hole + add_rectangular_pattern instead of twenty holes: one number changes the pitch.' It also names an applicability case ('works on sheet metal cuts too'). It does not, however, explicitly exclude cases or route to siblings such as add_circular_pattern for radial layouts.

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