Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

duplicate

Creates an independent or linked copy of an existing Blender scene object, with optional location, rotation, and scale values for direct placement.

Instructions

Duplicates an existing object in the scene with independent data blocks (deep copy) or linked data. Supports optional location, rotation_euler, and scale transforms for direct placement.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the existing object to duplicate.
scaleNoOptional size scale factors [sx, sy, sz] for the duplicate object.
linkedNoWhether to share the underlying datablock (linked copy) or create an independent deep copy. Defaults to False (independent).
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoOptional 3D world coordinates [x, y, z] to position the duplicate object.
new_nameNoOptional name for the newly created duplicate.
rotation_eulerNoOptional Euler rotation angles in radians [rx, ry, rz] for the duplicate object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses the deep-copy vs linked-datablock semantics and that transforms are applied for direct placement, but it says nothing about whether the source object is modified, what permissions or context are required, or what the call returns (e.g. the new object reference).

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?

Two tight sentences with the core behavior front-loaded and the optional transform support following. No filler or redundancy.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the copy semantics but omits the return value and any side effects on the original object, which an agent needs in order to chain calls correctly.

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 every parameter is already documented in the schema, including the linked/deep-copy default and the [x,y,z]/[rx,ry,rz] formats. The description only restates location, rotation_euler, and scale without adding format or constraint detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('Duplicates an existing object in the scene') and clarifies the two copy modes (deep copy vs linked data). It does not, however, distinguish itself from the sibling tool 'duplicate_object', so an agent cannot tell from the text alone which of the two to pick.

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?

The description implies when to use each mode by explaining 'independent data blocks (deep copy) or linked data', which is a real usage decision, but it gives no explicit when-to-use/when-not-to-use guidance, no prerequisites, and no routing to alternatives such as duplicate_object.

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