Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Mirror Components

mirror_components

Mirrors selected assembly components about a specified plane as instances of the same parts, useful for paired feet or brackets without creating new part files.

Instructions

Mirror assembly components about a plane, as instances of the same parts.

Use it for a part that appears on both sides, such as a pair of feet or brackets. Needs: an open assembly with the components and the plane. Changes: adds mirrored instances (no new part files). Returns: mirror with the plane and the added instances' names. A plane it doesn't have fails as not_found.

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": "mirror_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYes`components` and `plane`, both required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, non-destructive mutation, and the description adds real value on top: it discloses the effect ('adds mirrored instances (no new part files)') and an error mode ('a plane it doesn't have fails as not_found'). It does not address what happens on repeated invocation, which matters given idempotentHint=false.

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?

Three compact labeled clauses (purpose, Needs, Changes, Returns) with the core action front-loaded and zero filler. Each sentence delivers a distinct fact.

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?

With an output schema present and full parameter coverage, the description need not re-explain return shape, yet it summarizes Returns anyway. It covers preconditions, mutation effect, and failure mode; the only unaddressed item is repeat-call behavior for a tool explicitly marked non-idempotent.

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% and the plane parameter already enumerates example plane names, so the schema carries the parameter burden. The description only restates that both components and plane are required via the 'Needs' line, adding no new syntax or constraint detail beyond structured fields.

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 -- mirror assembly components about a plane -- and sharpens it with 'as instances of the same parts,' which distinguishes it from operations that create new part files. It does not explicitly name siblings like mirror_feature, pattern_components, or sketch_mirror, so the differentiation is left partly to inference, but 'assembly components' vs. a sketch or feature mirror is discernible.

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?

'Use it for a part that appears on both sides, such as a pair of feet or brackets' gives a concrete use-case, and 'Needs: an open assembly with the components and the plane' states prerequisites clearly. No competing alternative tool is named or excluded, which keeps it out of the top band.

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