Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

add_mirror

Mirror selected features or an entire solid across a plane in Autodesk Inventor to build symmetric parts from one half. Invalid mirrors that do not change the model are automatically reverted.

Instructions

Mirror features, or the whole body, across a plane. For a symmetric part model one half and mirror it — half the work, and it stays symmetric when a dimension changes. A mirror that changes nothing (the copy lands off the body or on the original) is taken back.

Args: features: Feature indices or names, ","-separated (manage_features list). Not with body=True. plane: Origin plane XY, XZ or YZ, or the name of a work plane. body: Mirror the whole solid; the two halves join where they meet on the plane. remove_original: With body=True: keep only the mirrored side (left-hand from right-hand part).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_mirror"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
planeNoYZ
featuresNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
remove_originalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavior: a no-op mirror is automatically rolled back, and body=True joins the halves at the plane. It does not say whether the operation is destructive to the source, what permissions or document state are required, or what happens on an invalid/offset plane.

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?

Front-loaded with the core action, followed by a brief rationale and an Args block that maps cleanly to the parameters. A little prose is spent on motivation ('half the work') but nothing is genuinely redundant.

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 5-parameter mutation tool with no annotations, the description supplies the mode separation, constraints, and rollback behavior; return values are covered by the output schema so needn't be explained. Only the multi-instance 'instance' parameter and failure modes are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20%, so the description must compensate, and mostly does: it defines features as a comma-separated list referring to manage_features, enumerates plane values (XY/XZ/YZ or a named work plane), explains body's join semantics, and ties remove_original to body=True. Only 'instance' is left to the schema's own description.

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?

Opens with a specific verb and resource ('Mirror features, or the whole body, across a plane') and immediately clarifies the two operating modes (feature mirror vs. whole-body mirror). It is clear what the tool produces, though it never contrasts itself with pattern/array siblings that could also replicate geometry.

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?

Gives a concrete scenario for use ('For a symmetric part model one half and mirror it') and states a mutual-exclusion rule ('features ... Not with body=True') plus a conditional for remove_original ('With body=True'). It stops short of naming an alternative tool or stating when not to mirror at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.