Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

delete_object

Safely removes an object from the active Blender scene, optionally unlinking unreferenced mesh, curve, camera, or light data; destructive changes require approval.

Instructions

Safely delete an object from the active scene, optionally unlinking its underlying datablock if no other objects reference it. Destructive operation requiring approval.

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>"
    },
    "name": "delete_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact name of the object to delete.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
unlink_dataNoWhether to remove the underlying mesh/curve/camera/light data if unreferenced (default True).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the important behaviors: the operation is destructive, the underlying datablock is only removed if unreferenced, and approval is required. It stops short of stating irreversibility, undo availability, or what happens to references/collections, and 'requiring approval' is left vague given that the schema's 'approved' argument is marked deprecated/untrusted, which could mislead an agent about the consent mechanism.

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?

Two sentences, front-loaded with the verb and scope, with no redundant restatement of the tool name. 'Safely' is slightly decorative given the immediately following 'Destructive operation', but the overall text is tight and readable.

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?

For a destructive four-parameter tool with no annotations and no output schema, the description covers purpose, destructiveness, conditional data removal, and an approval requirement. It is still incomplete on return value (no output schema, nothing said about what is returned on success or failure) and on the concrete approval workflow, which the sibling check_approval_status suggests exists.

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 100%, so all four parameters including name, task_id, approved, and unlink_data are already documented in the schema; the baseline is 3. The description's clause about unlinking data 'if no other objects reference it' adds a small amount of meaning beyond the schema's 'if unreferenced' wording, but it does not explain task_id or clarify how approval should actually be obtained.

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?

Specific verb plus resource plus scope: 'delete an object from the active scene', which separates it from siblings like delete_keyframe and delete_vse_strip that operate on other entity types. It does not name those siblings explicitly, so differentiation relies on the word 'object', but the intent is unambiguous.

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

Usage Guidelines3/5

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

The description implies when the tool applies (when an object in the active scene should be removed) and notes that approval is required, which is a prerequisite cue. However, it never states when NOT to use it, nor does it route the agent to alternatives such as duplicate_object or rename_object when deletion is the wrong choice, and the approval prerequisite is not actionable on its own.

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