Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duplicate_object

Copy any Blender object to create a new instance, optionally as a linked duplicate that shares mesh data. Returns the new object's name for further operations.

Instructions

Duplicate an object.

Args: object_name: Name of the object to duplicate. linked: If True, create a linked duplicate (shares mesh data). Defaults to False.

Returns: Dict with the new object's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedNo
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • addedInput schema / properties / object_name
      Added value: +{
+  "title": "Object Name",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "object_name"
+]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully explains that 'linked=True' creates a linked duplicate sharing mesh data, which is behavior beyond the schema. It still omits side effects such as whether the original object is preserved, whether the duplicate becomes selected, or what happens if the named object does not exist.

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?

The description is front-loaded and uses a clean Args/Returns structure with no wasted prose. The Returns line is somewhat redundant because an output schema exists, but the overall structure remains efficient.

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?

For a simple two-parameter duplication tool, the description covers both arguments, the linked-copy behavior, and the return value. It is nearly complete, though it lacks usage guidance and side-effect details that would matter in a larger object-manipulation workflow.

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 description coverage is 0%, so the description must compensate, and it does cover both parameters. The 'linked' argument receives a clear behavioral explanation and default value. The 'object_name' explanation is minimal and mostly restates the parameter name, so there is slight room for more detail.

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?

The description states a specific verb and resource: 'Duplicate an object.' This is clear enough for an agent to understand the core operation. However, it does not differentiate this tool from nearby siblings like create_object or duplicate_material, leaving an agent to infer the distinction from the name alone.

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?

The description provides no when-to-use guidance, no prerequisites, and no alternatives. It only documents arguments and returns, so an agent receives no help deciding between duplicate_object, create_object, or duplicate_material.

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