Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

boolean_operation

Apply UNION, DIFFERENCE, or INTERSECT operations between two Blender objects using a non-destructive boolean modifier.

Instructions

Perform a boolean operation between two objects using a modifier.

NOTE: For destructive booleans, prefer the booltool_auto_* tools instead (booltool_auto_union, booltool_auto_difference, booltool_auto_intersect, booltool_auto_slice). They handle selection and cutter cleanup automatically. Use this tool only when you need a non-destructive boolean modifier workflow.

Args: object_name: Name of the object to apply the boolean to. target_name: Name of the target/cutter object. operation: Boolean operation type. One of: UNION, DIFFERENCE, INTERSECT.

Returns: Confirmation dict with operation details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoDIFFERENCE
object_nameYes
target_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / operation / enum
      Added value: +[
+  "DIFFERENCE",
+  "INTERSECT",
+  "UNION"
+]
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, so the description carries the load, and it does disclose the key trait: this is a non-destructive modifier workflow that does NOT handle selection or cutter cleanup automatically. It also states the return shape. It stops short of saying whether the cutter is hidden/consumed or whether the modifier is applied, which matters for a mutation tool with zero annotation coverage.

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?

Front-loaded with the core purpose, then a clearly marked NOTE routing to alternatives, then Args and Returns. Well structured and skimmable; the NOTE is slightly verbose in repeating all four sibling names but earns its place as routing guidance.

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?

With an output schema present, the return-value explanation is redundant but harmless. Together with usage routing and per-parameter documentation, the definition is nearly complete; the only real gap is lifecycle behavior of the cutter object, which is not addressed.

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 0%, and the description compensates by documenting all three parameters, notably clarifying that target_name is the 'target/cutter object' — meaning beyond the bare schema title. The enum values for operation are restated from the schema, so the gain is uneven but the cutter semantics are genuinely additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (boolean operation between two objects) plus the mechanism (using a modifier), and explicitly differentiates itself from the booltool_auto_* siblings by naming them. An agent can tell exactly which tool fits which situation.

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

Usage Guidelines5/5

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

Gives explicit when-not guidance ('For destructive booleans, prefer the booltool_auto_* tools') with all four alternatives named, and states the condition that selects this tool ('non-destructive boolean modifier workflow'). No inference required.

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