Skip to main content
Glama

modify_object

Adjust location, rotation, scale, or visibility of objects in Blender scenes to refine 3D models and scenes.

Instructions

Modify an existing object in the Blender scene.

Parameters:
- name: Name of the object to modify
- location: Optional [x, y, z] location coordinates
- rotation: Optional [x, y, z] rotation in radians
- scale: Optional [x, y, z] scale factors
- visible: Optional boolean to set visibility

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
locationNo
rotationNo
scaleNo
visibleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'modify_object' MCP tool. It constructs parameters from inputs and sends a 'modify_object' command to the Blender connection via get_blender_connection(). The @mcp.tool() decorator registers it as an MCP tool. The function signature and docstring define the input schema.
    @mcp.tool()
    def modify_object(
        ctx: Context,
        name: str,
        location: List[float] = None,
        rotation: List[float] = None,
        scale: List[float] = None,
        visible: bool = None,
    ) -> str:
        """
        Modify an existing object in the Blender scene.
    
        Parameters:
        - name: Name of the object to modify
        - location: Optional [x, y, z] location coordinates
        - rotation: Optional [x, y, z] rotation in radians
        - scale: Optional [x, y, z] scale factors
        - visible: Optional boolean to set visibility
        """
        try:
            # Get the global connection
            blender = get_blender_connection()
    
            params = {"name": name}
    
            if location is not None:
                params["location"] = location
            if rotation is not None:
                params["rotation"] = rotation
            if scale is not None:
                params["scale"] = scale
            if visible is not None:
                params["visible"] = visible
    
            result = blender.send_command("modify_object", params)
            return f"Modified object: {result['name']}"
        except Exception as e:
            logger.error(f"Error modifying object: {str(e)}")
            return f"Error modifying object: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'modify an existing object,' implying mutation, but lacks critical behavioral details: whether changes are reversible, what permissions are needed, how errors are handled (e.g., if object doesn't exist), or if there are rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by a bulleted list of parameters. There's no wasted text, but the structure could be slightly improved by integrating parameter details more seamlessly rather than as a separate list.

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 5 parameters with 0% schema coverage and no annotations, the description is moderately complete: it covers the purpose and parameters. However, as a mutation tool, it lacks behavioral context (e.g., side effects, error handling). The presence of an output schema (not shown) reduces the need to explain return values, but overall completeness is adequate with clear gaps.

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?

Schema description coverage is 0%, so the description must compensate. It lists all 5 parameters with brief explanations (e.g., 'Optional [x, y, z] location coordinates'), adding basic semantics beyond the schema's titles. However, it doesn't clarify units (e.g., radians for rotation), constraints (e.g., array length must be 3), or interactions between parameters, leaving gaps in understanding.

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 'modify' and resource 'existing object in the Blender scene,' making the purpose immediately understandable. It distinguishes from siblings like 'create_object' and 'delete_object' by specifying modification rather than creation or deletion. However, it doesn't explicitly differentiate from tools like 'set_material' or 'set_texture' that might also modify objects in different ways.

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 prerequisites (e.g., object must exist), exclusions (e.g., not for creating new objects), or comparisons to siblings like 'set_material' for material changes. The agent must infer usage from the name and parameter list 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