Skip to main content
Glama

create_object

Add 3D objects to Blender scenes by specifying type, location, rotation, and scale parameters for scene composition.

Instructions

Create a new object in the Blender scene.

Parameters:
- type: Object type (CUBE, SPHERE, CYLINDER, PLANE, CONE, TORUS, EMPTY, CAMERA, LIGHT)
- name: Optional name for the object
- location: Optional [x, y, z] location coordinates
- rotation: Optional [x, y, z] rotation in radians
- scale: Optional [x, y, z] scale factors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoCUBE
nameNo
locationNo
rotationNo
scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'create_object' MCP tool. It is decorated with @mcp.tool() for automatic registration. The function constructs parameters from inputs, sends a 'create_object' command to the Blender addon via socket, and returns a success message with the created object's name.
    @mcp.tool()
    def create_object(
        ctx: Context,
        type: str = "CUBE",
        name: str = None,
        location: List[float] = None,
        rotation: List[float] = None,
        scale: List[float] = None,
    ) -> str:
        """
        Create a new object in the Blender scene.
    
        Parameters:
        - type: Object type (CUBE, SPHERE, CYLINDER, PLANE, CONE, TORUS, EMPTY, CAMERA, LIGHT)
        - name: Optional name for the object
        - location: Optional [x, y, z] location coordinates
        - rotation: Optional [x, y, z] rotation in radians
        - scale: Optional [x, y, z] scale factors
        """
        try:
            # Get the global connection
            blender = get_blender_connection()
    
            # Set default values for missing parameters
            loc = location or [0, 0, 0]
            rot = rotation or [0, 0, 0]
            sc = scale or [1, 1, 1]
    
            params = {"type": type, "location": loc, "rotation": rot, "scale": sc}
    
            if name:
                params["name"] = name
    
            result = blender.send_command("create_object", params)
            return f"Created {type} object: {result['name']}"
        except Exception as e:
            logger.error(f"Error creating object: {str(e)}")
            return f"Error creating object: {str(e)}"
  • The docstring provides detailed input schema/parameter descriptions for the create_object tool, specifying types, defaults, and valid values (e.g., primitive types).
    """
    Create a new object in the Blender scene.
    
    Parameters:
    - type: Object type (CUBE, SPHERE, CYLINDER, PLANE, CONE, TORUS, EMPTY, CAMERA, LIGHT)
    - name: Optional name for the object
    - location: Optional [x, y, z] location coordinates
    - rotation: Optional [x, y, z] rotation in radians
    - scale: Optional [x, y, z] scale factors
    """
  • src/server.py:318-318 (registration)
    The @mcp.tool() decorator registers the create_object function as an MCP tool.
    @mcp.tool()
  • Reference to create_object in the asset_creation_strategy prompt, guiding when to use it.
    - create_object() for basic primitives (CUBE, SPHERE, CYLINDER, etc.)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this creates a new object but doesn't cover important aspects like whether this requires specific permissions, if it's destructive to existing scene elements, what happens on failure, or typical response behavior. The description is minimal beyond the basic action.

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?

The description is perfectly structured and concise. It starts with the core purpose in one sentence, then provides a clean bulleted list of parameters with clear explanations. Every sentence earns its place with no wasted words.

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?

Given that there's an output schema (which handles return values), no annotations, and 5 parameters with good description coverage, the description is reasonably complete for the basic operation. However, for a creation tool in a 3D modeling context, it could benefit from mentioning typical use cases, limitations, or integration with other tools.

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?

The description provides excellent parameter semantics that compensate for the 0% schema description coverage. It clearly explains what each parameter represents (object type with specific enum values, optional name, location coordinates, rotation in radians, scale factors), adding substantial meaning beyond the bare 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?

The description clearly states the verb ('Create') and resource ('new object in the Blender scene'), making the purpose immediately understandable. However, it doesn't distinguish this tool from siblings like 'create_3d_model_from_image' or 'create_3d_model_from_text', which also create objects but through different methods.

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 guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'create_3d_model_from_image' (for creating from images) or 'modify_object' (for editing existing objects), leaving the agent to guess based on tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VAST-AI-Research/tripo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server