Skip to main content
Glama
Sign In
Blender MCP

Blender MCP

by harveyxiacn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender_object_parent

Idempotent

Set a parent-child relationship between Blender objects, or clear an existing one, with an option to preserve world transforms.

Instructions

Set the parent-child relationship for objects.

Args: params: Child object and parent object names

Returns: Setting result

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations provide idempotentHint=true and destructiveHint=false, indicating safe mutation. The description adds no further behavioral details such as side effects on object transforms or interaction with existing parent relationships. It does not contradict annotations.

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?

Extremely concise at two sentences, front-loaded with the primary action. No redundant information, every part serves a purpose.

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?

While the tool is simple and annotations cover safety, the description lacks details about return value (just 'Setting result'), error handling, or prerequisites. It is adequate but not fully complete for an agent unfamiliar with the domain.

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?

The input schema already includes clear descriptions for each parameter (child_name, parent_name, keep_transform). The tool's description only summarizes 'Child object and parent object names', adding minimal value. Schema coverage is effectively high, so baseline score applies.

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

Purpose5/5

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

The description 'Set the parent-child relationship for objects' clearly states the action and resource. The title from annotations reinforces this. It is distinct from sibling tools which handle other object operations like transforms, creation, deletion, etc.

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?

No guidance on when to use this tool versus alternatives, prerequisites, or contexts where it should be avoided. There is no mention of when to set vs clear parent, or how it relates to other hierarchy tools like blender_describe_hierarchy.

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