Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Mirror Sketch Entities

sketch_mirror

Mirror sketch entities about a centreline to build symmetric profiles: draw one half, add a centreline, then copy it across for a complete mirrored sketch.

Instructions

Mirror sketch entities about a centreline in the open sketch.

Use it for symmetric profiles: draw one half, add a centreline with add_centerline, then mirror. Needs: an open sketch (create_sketch). Changes: adds mirrored copies. Returns: mirror with id, entities and mirror_line.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesA mapping: `entities` (ids to mirror) and `mirror_line` (the centreline's id).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds the substantive point that the operation is additive ('adds mirrored copies') and requires an open sketch, which is real behavioral context beyond the annotations. It does not detail failure cases (e.g. no centreline present) or whether repeated calls duplicate entities despite 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?

Front-loaded purpose sentence followed by short labeled clauses (Use it / Needs / Changes / Returns). Every sentence contributes; no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a fully described schema, and an output schema (so return values need not be explained in depth), the description covers purpose, prerequisites, side effects and the sibling to call first. An agent has everything needed to invoke it correctly.

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 coverage is 100% and the nested input_data already documents `entities` and `mirror_line`, so the schema carries the burden. The description only echoes those names via the workflow and 'Returns' line, adding no syntax or format detail beyond the schema.

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 (mirror), resource (sketch entities) and scope (about a centreline in the open sketch). The 'in the open sketch' qualifier implicitly separates it from the feature-level sibling mirror_feature, so an agent can pick the right one from the description alone.

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?

Explicitly prescribes the workflow ('draw one half, add a centreline with add_centerline, then mirror') and names the prerequisite sibling create_sketch. It lacks an explicit when-not/alternative clause (e.g. use mirror_feature for solid features), which keeps it below a 5.

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