Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Pattern Components

pattern_components

Repeat assembly components in linear or circular patterns along or around a reference axis, defining count, spacing, or angle for rows of bolts or parts around a hub.

Instructions

Repeat assembly components in a row along an axis, or around one.

Use it for a row of bolts or pins, or parts around a hub. axis names a reference axis (create_axis in the assembly); count includes the seeds. Linear takes spacing (mm); circular takes angle (degrees, 360 spaces them equally). The row runs along the axis's own direction, which SolidWorks picks (an x axis from create_axis runs toward -x), so check the result with verify_model's bounding box. Needs: an open assembly with the seeds and the axis. Changes: adds a component pattern feature. Returns: pattern with the feature name, the component counts before and after and the added instances.

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": {
      "input_data": "<input_data>"
    },
    "name": "pattern_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYes`components`, `axis` and `count` are required; `kind` (`linear`) with `spacing`, or `circular` with `angle`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses that the operation 'adds a component pattern feature' and, crucially, that the row direction is chosen by SolidWorks ('an x axis... runs toward -x'), with a recommendation to confirm via `verify_model`'s bounding box. That hidden-direction quirk is exactly the kind of behavior an agent would otherwise get wrong; the main omission is failure modes, e.g. what happens with an invalid or too-large count.

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 purpose is front-loaded in the first sentence, followed by compact blocks for use cases, semantics, prerequisites, changes and returns. A few parentheticals are dense, but no sentence is filler.

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 a single-parameter (nested-object) mutation tool, the definition covers prerequisites, mode selection, output naming and a verification step; an output schema exists so the return-value description is a bonus rather than a necessity. Left uncovered are error conditions and the limits of `count`, the only real completeness gap.

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?

Schema description coverage is 100%, so the schema already defines `axis`, `kind`, `angle`, `spacing` and `components`. The description adds a little framing (count includes seeds; spacing in mm; angle in degrees where 360 spaces equally) and pairs `kind` with its companion parameter, but most of that restates the schema text rather than adding new meaning.

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?

The description opens with a specific verb and resource: 'Repeat assembly components in a row along an axis, or around one,' which covers both linear and circular modes via the `kind` parameter. It never names the sibling tools `pattern_linear` or `pattern_circular`, so an agent has to infer that those are separate entry points for the two modes it describes here.

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?

It gives concrete use-case examples ('a row of bolts or pins, or parts around a hub') and states the precondition: 'Needs: an open assembly with the seeds and the axis.' There is no explicit when-not guidance and no routing to `pattern_circular`/`pattern_linear` if the agent wants a mode-specific call.

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