Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

mirror_feature

Mirror selected SOLIDWORKS features across the Front, Top, Right, named planes, or a flat face, and get a warning when the mirrored copy has no effect.

Instructions

Mirror one or more features about a plane (Front, Top, Right or any plane by name) or about a flat body face. Warns if the mirrored copy has no effect.

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": {
      "plane": "<plane>"
    },
    "name": "mirror_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
planeYesFront, Top, Right, a plane name (e.g. 'Plane1'), or 'face' to mirror about the flat face at face_x/face_y/face_z
face_xNoX of a point on the mirror face (plane='face' only)
face_yNoY of a point on the mirror face (plane='face' only)
face_zNoZ of a point on the mirror face (plane='face' only)
featuresNoFeature names from list_features. Default: the last solid feature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully notes that the tool warns if the mirrored copy has no effect, but it does not disclose document-state requirements, mutation effects, return behavior, or other operational constraints expected for a modeling operation.

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?

The description is two sentences, front-loaded with the core action and scope. Every sentence contributes useful information without unnecessary wording.

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

Completeness3/5

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

The schema is rich and covers all parameters, and no output schema exists, so the description need not explain return values. However, for a mutation tool with no annotations, it remains thin on operational context such as required document state and side effects.

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 input schema already documents all parameters, including the plane options, face coordinates, unit values, and default feature selection. The description adds little parameter meaning beyond what the schema already supplies, so the baseline of 3 is appropriate.

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 states a specific verb and resource: mirroring one or more features about a plane or flat face. It does not explicitly differentiate this operation from sibling tools such as circular_pattern or other feature-creation tools, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but gives no explicit guidance on when to use it versus alternatives. There is no mention of prerequisites, when not to use it, or how it relates to sibling pattern or feature tools.

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