Skip to main content
Glama

Mirrored

mirrored

Creates a reflected copy of a PartDesign feature across a specified plane, including origin, datum, or face-defined planes.

Instructions

Mirror a PartDesign feature across a plane.

plane: 'XY'|'XZ'|'YZ' for body origin planes, a datum-plane handle string, or {handle, face: tag|'FaceN'} for a face-defined mirror plane.

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": {
      "feature": "<feature>"
    },
    "name": "mirrored"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMirrored
planeNoYZ
featureYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows this is a non-destructive local mutation. The description adds useful detail about plane specification but never states that it creates a new 'Mirrored' feature in the tree, whether it is additive/replaceable, or that the result depends on the body's existing state. Adequate, not rich.

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?

Two short sentences, front-loaded with the core action, followed by a compact enumeration of plane forms. No filler; only minor cost is the slightly cryptic 'datum-plane handle string' and 'tag|FaceN' shorthand with no pointer to resolve_face/resolve_edge.

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

Completeness2/5

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

For a modeling mutation with four parameters, no output schema, and a required but undocumented feature identifier, the description leaves too much open: what a feature reference looks like, whether the mirror lands in the same body, and how success is reported. The plane explanation is good but does not cover the rest of the calling contract.

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 25%, and the description fully compensates for the 'plane' parameter with concrete accepted forms ('XY'|'XZ'|'YZ', datum-plane handle, or {handle, face}). However the required 'feature' parameter, arguably the most important, is left entirely undefined in both schema and description, as are 'name' and 'workspace'.

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: 'Mirror a PartDesign feature across a plane.' That is unambiguous. It doesn't contrast itself with near-neighbors like linear_pattern, polar_pattern, or transform, which also duplicate/array geometry, so the agent must infer the distinction.

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?

There is no guidance on when to use this tool versus linear_pattern, polar_pattern, transform, or copy_shape, and no stated preconditions (feature must exist, must belong to a PartDesign body, must be in an active document/workspace). Usage is only implied by the phrase 'PartDesign feature'.

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