Skip to main content
Glama
solidworks-mcp

solidworks-mcp

linear_pattern

Repeats selected SolidWorks features along a model axis by specifying total copies and spacing, with an optional second direction for grid patterns.

Instructions

Repeats features (names from get_feature_tree) in a row along a model axis: count copies in total (original included), spacing_mm apart, towards + (or - with reverse). direction2/count2/spacing2_mm add a second direction for a grid. The first use of an axis adds a hidden reference axis "Axis X (MCP)" (Y, Z) 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>",
      "direction": "<direction>",
      "count": "<count>",
      "spacing_mm": "<spacing_mm>"
    },
    "name": "linear_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of copies along direction 1 (including original, >= 2)
count2NoNumber of copies along direction 2 (>= 1)
reverseNo
featuresYes
reverse2No
directionYes
direction2No
spacing_mmYesSpacing between copies in mm
spacing2_mmNoSpacing between copies in direction 2 in mm

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-idempotent mutation. The description adds a genuine side effect not in annotations: the first use of an axis injects a hidden reference axis 'Axis X (MCP)' into the tree. That is exactly the kind of state change an agent needs to know before calling.

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?

Three short sentences, front-loaded with the core behavior and the parameter meaning, with no filler. Density is high but every clause carries information; only the axis-naming sentence is slightly tangential to invocation.

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 no explanation, and the description covers the mutation's main side effect plus most parameter semantics. What remains thin is guidance on choosing this tool versus the sketch or circular pattern siblings.

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 44% schema description coverage, the description must compensate, and it largely does: it clarifies that count includes the original, that reverse flips the direction sign, and that direction2/count2/spacing2_mm form a second direction for a grid. reverse2 is left unexplained, a minor gap against the nine parameters.

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 ('Repeats features ... in a row along a model axis') plus scope details (count includes original, spacing_mm apart, direction with reverse). The phrase 'model axis' implicitly separates it from sketch-level patterning, but it never names sketch_linear_pattern or circular_pattern, so differentiation rests on inference.

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 one useful prerequisite pointer: feature names come from get_feature_tree. There is no explicit statement of when to prefer this over sketch_linear_pattern or circular_pattern, and no exclusion conditions, so usage is only implied by the 'model axis' wording.

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