Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Mirror Feature

mirror_feature

Mirror solid bodies or features about a chosen plane to build symmetric parts; use body mirroring for lofts and sweeps, or feature mirroring for cuts that need named features.

Instructions

Mirror solid bodies or features of the active part about a plane.

Use it for symmetric parts: model one half, then mirror. Body mirroring (the default) is what works for lofts and sweeps; to mirror a cut, name the cut and set mirror_bodies off. It fails when the volume doesn't change, which means nothing was mirrored. Needs: an open part with the named bodies or features. Changes: adds a Mirror feature. Returns: mirror with name, mirrored, mirror_plane, merge, mirror_bodies, and volume_before, volume_after and volume_change (mm³, negative for a cut).

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_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe mirror. `features` (at least one name) and `mirror_plane` (e.g. "Right Plane") are required; `merge` and `mirror_bodies` are on.

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?

Annotations already establish that this is a non-read-only, non-idempotent, non-destructive write, and the description adds real substance on top: the prerequisite of an open part with named bodies/features, the side effect of adding a Mirror feature, and a failure mode tied to unchanged volume. That failure statement is slightly vague about whether it raises an error or silently no-ops.

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 and the guidance is compact, with mode selection and prerequisites in tight sentences. The trailing enumeration of return fields is somewhat redundant given the output schema exists, but it does not bloat the definition.

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 write tool with nested parameters, the description covers prerequisites, mode choice, side effects, and failure conditions, which is close to complete. Its only shortfall is not routing the agent away from sketch_mirror for sketch geometry, and restating return fields the output schema already defines.

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 nested schema already explains `features`, `mirror_plane`, `merge`, and `mirror_bodies` in detail. The description reinforces the defaults and the cut workflow, but most of that meaning is already in the schema, so it lands at the baseline rather than adding new semantics.

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 first sentence gives a specific verb and resource: 'Mirror solid bodies or features of the active part about a plane.' Scoping to solid bodies and features of the active part implicitly separates it from sketch_mirror, but no sibling is named, so an agent must infer that distinction.

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 supplies a concrete usage pattern ('model one half, then mirror') and a decision rule between the two modes: body mirroring for lofts and sweeps, feature mirroring for cuts with `mirror_bodies` off. It stops short of stating when to prefer sketch_mirror or another approach instead.

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