Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

purge_orphans

Removes unused orphaned Blender datablocks from memory to free space; irreversible operation deletes unlinked meshes, materials, textures, curves, and actions.

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_orphans"
  }
}

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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses irreversibility and enumerates the datatypes destroyed (meshes, materials, textures, curves, actions) and clarifies that purging happens 'from memory'. It stops short of explaining the safety implications of the recursive and linked-library defaults, which materially change blast radius.

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 sentences, correctly front-loaded: what it does first, then a prominent WARNING with the concrete consequences. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, zero-required-parameter tool with no annotations and no output schema, the description supplies the essentials: mechanism, scope, and irreversibility. The remaining gap is disambiguation from purge_orphaned_datablocks and a note on how the linked/recursive defaults expand what is destroyed.

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 the schema already documents do_local_ids, do_recursive, do_linked_ids, and the deprecated 'approved' flag with its untrusted-input warning. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

States a specific verb (purges) and resource (unused/orphaned/zero-user Blender datablocks) and even names the underlying API call bpy.data.orphans_purge. It does not, however, distinguish itself from the sibling purge_orphaned_datablocks, whose name suggests identical behavior — that ambiguity is left for the agent to resolve.

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?

Usage is only implied: the parenthetical '(orphaned, zero-user)' defines the condition under which something is purged, so an agent can infer this is cleanup for unlinked data. There is no explicit when-to-use/when-not guidance, no prerequisites, and no mention of the near-duplicate sibling as an alternative.

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