Skip to main content
Glama

set_object_parent

Parent one Blender object to another while optionally preserving its transform, enabling scene organization and hierarchical relationships without shifting placement.

Instructions

Parent 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>",
      "parent": "<parent>"
    },
    "name": "set_object_parent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
parentYes
keep_transformNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations provided, the description bears the entire burden and supplies nothing: it does not say whether parenting preserves world transform, what happens to existing children or an existing parent, whether the operation is reversible, or whether it mutates the named object. For a scene-graph mutation this is a serious gap.

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?

Three words with zero wasted clauses, but this is under-specification rather than conciseness; there is effectively no structure because there is nothing to structure.

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

Completeness1/5

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

An output schema exists, so return values need not be explained, but a mutation tool with three undocumented parameters, no annotations, and no behavioral detail leaves the agent unable to invoke it safely or predictably.

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% across three parameters. The description never explains whether "name" is an object name or path, whether "parent" is an object name or a collection, or what keep_transform=true actually means (retain world position vs. snap to parent space). The single parameter with real behavioral consequence is left completely undefined.

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?

"Parent an object" restates the tool name set_object_parent almost verbatim, so it adds no information the agent did not already have from the identifier. It does at least imply a scene-graph parenting relationship rather than a generic setting change, but that is the full extent of its clarity.

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

Usage Guidelines1/5

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

No when-to-use context, no preconditions, and no mention of the obvious counterpart unparent_object or of how this differs from move_object_to_collection. The agent gets no help choosing this tool over its siblings.

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