Skip to main content
Glama

delete_object

Remove objects from Blender scenes by specifying their names. This tool helps manage 3D assets by deleting unwanted elements from your workspace.

Instructions

Delete an object from the Blender scene.

Parameters:
- name: Name of the object to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'delete_object' MCP tool. It is decorated with @mcp.tool() for registration and implements the logic to delete a Blender object by name via a socket command to the Blender addon.
    @mcp.tool()
    def delete_object(ctx: Context, name: str) -> str:
        """
        Delete an object from the Blender scene.
    
        Parameters:
        - name: Name of the object to delete
        """
        try:
            # Get the global connection
            blender = get_blender_connection()
    
            result = blender.send_command("delete_object", {"name": name})
            return f"Deleted object: {name}"
        except Exception as e:
            logger.error(f"Error deleting object: {str(e)}")
            return f"Error deleting object: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits such as whether deletion is permanent, requires specific permissions, affects scene hierarchy, or has side effects like removing associated materials. This is inadequate for a destructive operation.

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 extremely concise with two sentences: one stating the purpose and another listing parameters. It's front-loaded with the core action and wastes no words, making it easy to parse quickly.

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 the tool's destructive nature, lack of annotations, and presence of an output schema (which might cover return values), the description is minimally adequate. It covers the basic action and parameter but misses important context like safety warnings or usage scenarios, leaving gaps for a mutation tool.

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 adds meaningful context for the single parameter by specifying it's the 'Name of the object to delete', which clarifies its role beyond the schema's generic 'Name' title. With 0% schema description coverage and only one parameter, this compensates well, though it doesn't detail format or constraints.

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 action ('Delete') and resource ('object from the Blender scene'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'modify_object' or 'create_object' beyond the verb, which prevents a perfect score.

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 is provided on when to use this tool versus alternatives like 'modify_object' or 'create_object', nor any prerequisites or exclusions. The description only states what it does, not when it's appropriate.

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