Skip to main content
Glama

duplicate_object

Create a copy of an existing object in Blender, optionally as a linked duplicate or with a new name, to reuse geometry without rebuilding it.

Instructions

Duplicate an object.

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
nameYes
linkedNo
new_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden, and it does not. It does not say what is copied exactly, which collection the copy lands in, whether the copy is independent or linked, or what the operation returns, even though the output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short, but its brevity comes from under-specification rather than from tight writing. There is no front-loaded detail because there is no detail at all.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers returns, but for a three-parameter tool with a domain-specific 'linked' and 'new_name' pair and no annotations, this description is far too thin. An agent could call it, but it could not predict what it does.

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

Parameters1/5

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

Schema description coverage is 0%, and none of the three parameters (name, linked, new_name) are explained. The meaning of 'linked' and the interaction between 'name' and 'new_name' are completely undocumented here and in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

'Duplicate an object' restates the tool name almost word for word and names only a verb plus a generic resource. It gives no hint of scope, such as whether the copy keeps modifiers, materials, or transforms, and it does not differentiate the tool from siblings like create_object.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as create_object, and no prerequisites. An agent cannot tell from the description whether to duplicate or create an object instead.

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