Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

purge_orphaned_datablocks

Removes unused (orphaned, zero-user) Blender datablocks from memory to reduce clutter, with optional recursive purging of newly orphanned items.

Instructions

Safely purges unused (orphaned, zero-user) Blender datablocks from memory using bpy.data.orphans_purge. WARNING: Potentially irreversible operation that removes unlinked meshes, materials, textures, curves, and actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "purge_orphaned_datablocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
do_local_idsNoWhether to purge local datablocks. Defaults to True.
do_recursiveNoWhether to recursively purge datablocks that become orphaned during the purge pass. Defaults to True.
do_linked_idsNoWhether to purge linked datablocks from external libraries. Defaults to 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?

With no annotations supplied, the description carries the full burden, and it does disclose the key risk: the operation is potentially irreversible and enumerates the datablock types removed. However, it omits the most consequential behavior — that do_linked_ids defaults to true and can purge data from external libraries — and says nothing about approval requirements, despite the schema carrying an 'approved' flag.

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?

Two tight sentences: the operation and its mechanism first, then the risk warning. Nothing is redundant and the warning is placed where a scanning agent will see it.

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 five-parameter, unannotated, no-output-schema destructive tool, the definition covers the headline risk but leaves important behavior unexplained — notably the default-on recursive and linked-library purging and the fact that the approval parameter is untrusted. An agent could invoke this with defaults and unintentionally strip external library data.

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?

Schema description coverage is 100%, so every parameter is already documented, and the description correctly stays out of restating them. It adds marginal meaning by framing the purge as operating on memory and by naming the affected datablock classes, which helps interpret what do_local_ids and do_linked_ids actually control.

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 states a specific verb and resource ('purges unused (orphaned, zero-user) Blender datablocks') and even names the underlying API call (bpy.data.orphans_purge). It does not explicitly differentiate itself from the sibling 'purge_orphans', so an agent must infer the distinction, but the operation itself 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as the sibling purge_orphans tool. The only implied usage is 'when datablocks are orphaned', which the agent must derive from the definition of orphaned itself.

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