Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

duplicate_object

Duplicate an existing Blender object as an independent deep copy or linked copy, optionally applying location, rotation, and scale 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_object"
  }
}

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

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the deep-copy vs. shared-datablock semantics and that transforms can be applied at creation, but it is silent on side effects such as whether the duplicate becomes selected/active, whether linked copies propagate later edits, and whether name collisions are handled.

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 compact sentences with the core behavior and the optional placement capability front-loaded. No filler, though the transform list slightly duplicates the schema.

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 core copy-mode decision but omits what a caller gets back (new object identity/name) and ignores the deprecated 'approved' flag and 'task_id', which an agent must learn solely from the schema.

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 including linked, new_name, and the transform vectors is already documented in structured form; baseline 3 applies. The description only restates location, rotation_euler, and scale as 'optional transforms for direct placement' without adding format or ordering detail beyond the schema.

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 immediately qualifies the two output modes: independent deep copy vs. linked data. This is clearly distinct from a generic transform or rename, though it does not explicitly contrast with the sibling 'duplicate' tool, leaving some ambiguity an agent must resolve on its own.

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 usage through the linked/independent distinction, which is a real decision point, but it never says when to pick this tool over the 'duplicate' sibling or when not to use it. No prerequisites (object mode, selection state, existing name) are stated.

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