Power CAD MCP

by khs0927

Overview Schema Source Related Servers Discussions Admin

Hybrid

mirror_entities

Create a mirrored copy of CAD entities across the line p1-p2, retaining originals unless delete_source is true.

Instructions

Mirror entities across the line p1-p2 (keeps the originals unless delete_source).

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": {
      "handles": "<handles>",
      "p1": "<p1>",
      "p2": "<p2>"
    },
    "name": "mirror_entities"
  }
}

Input Schema

Name	Required	Description
`p1`	Yes	[x, y] or [x, y, z]
`p2`	Yes	[x, y] or [x, y, z]
`handles`	Yes	Entity handles (hex strings)
`delete_source`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false. The description usefully explains the default source-preserving behavior that justifies the non-destructive hint, but says nothing about permissions, what happens to the originals when delete_source=true, or how the mirror is computed in 3D.

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?

A single front-loaded sentence that packs the operation, the axis, and the default behavior with no filler.

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?

An output schema exists so return values need no explanation, and annotations carry the safety profile. The description is nearly complete for a 4-parameter transform, though it could note the optional destructive behavior enabled by delete_source.

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 75%, and the description compensates for the one undocumented parameter by explaining delete_source's effect on the originals. p1/p2 and handles formats are already covered by 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), the resource (entities), and the exact transform axis (the line p1-p2), which cleanly separates it from siblings like move_entities, rotate_entities and copy_entities.

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

Usage Guidelines3/5

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

Usage is only implied: 'keeps the originals unless delete_source' hints at the copy-vs-move distinction but never states when to choose this over copy_entities or offset_entity.

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