Skip to main content
Glama

Copy Shape

copy_shape

Create an independent static solid copy of a shaped object, so later edits to the original do not affect the duplicate. Use it to seed mirrors, patterns, or standalone assembly instances.

Instructions

Duplicate a shaped object as an INDEPENDENT static solid.

Unlike add_part (which creates an App::Link that tracks the source), this deep-copies the geometry: later edits to the original do NOT propagate to the copy. Use it to seed a mirror/pattern, or to drop a standalone duplicate instance into an assembly.

handle: handle of the source object (must have a Shape). placement: optional absolute [x, y, z] translation in mm applied to the copy's base. Omit to leave the copy coincident with the source. The source object is unchanged and stays visible. name: optional name for the new object (default '_copy').

Returns {handle, name, volume}: handle is a new 'copy_N' handle, name is the FreeCAD object name, volume is the copied solid's volume in mm^3.

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": {
      "handle": "<handle>"
    },
    "name": "copy_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
handleYes
placementNo
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

A5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false): it discloses that the copy is deep-copied, that later edits to the original do NOT propagate, that the source object is unchanged and stays visible, and the default naming scheme. It also documents the return payload shape, which no output schema provides.

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-loads the single most decision-relevant fact (independent static solid vs. tracked link) in the first two sentences, then uses a compact per-parameter block and a one-line return contract. Every sentence carries information; nothing is repeated from the schema.

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?

For a 4-parameter mutation tool with no output schema, the description covers the copy semantics, side-effect profile on the source, parameter formats, and the return value {handle, name, volume}. There is nothing further an agent would need before invoking it correctly.

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

Parameters5/5

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

Schema description coverage is only 25% (only 'workspace' is documented in the schema), so the description must carry the load — and it does, explaining that handle must reference an object with a Shape, that placement is an optional absolute [x,y,z] translation in mm with a defined omit behaviour, and that name defaults to '<SourceName>_copy'.

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 and resource ('Duplicate a shaped object as an INDEPENDENT static solid') and immediately distinguishes it from the closest sibling by naming add_part and explaining its App::Link tracking behaviour. An agent can select between copy_shape and add_part without inspecting either schema.

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

Usage Guidelines5/5

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

Gives an explicit contrast case against add_part ('which creates an App::Link that tracks the source') and two concrete use cases ('seed a mirror/pattern', 'drop a standalone duplicate instance into an assembly'). The condition selecting this tool over its alternative is spelled out rather than implied.

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