Skip to main content
Glama

Boolean Op

boolean_op

Perform Boolean cut, fuse, or intersection on two existing 3D objects by their handles. Identifies degenerate cuts that remove nothing or everything, returning warnings, with strict mode to turn them into errors.

Instructions

Boolean operation on two existing objects, referenced by their handles.

op: 'cut' (base minus tool), 'fuse' (union), or 'common' (intersection). base, tool: handles returned from add_primitive (e.g. 'box_1', 'cylinder_1'). strict: raise instead of warning on a degenerate cut (see below).

Returns {handle, volume, removed_volume, volume_ratio}, plus warnings — a list of strings — ONLY when the cut looks degenerate; the key is absent on a clean op, so "warnings" in result is the test. removed_volume: base_volume - result_volume, mm3. Positive means material went away (always so for cut/common); NEGATIVE on a fuse, where it is the volume the tool added. volume_ratio: result_volume / base_volume, or None when the base was empty. The two warned cases are cut-only, and each means the cut did not do what was asked: annihilation (result ~ 0 — the tool swallowed the base, so every later feature operates on nothing) and miss (result == base — the tool never intersected the base, so nothing was removed). Warn-don't-fail is the default because cutting everything away is legitimate in some workflows; pass strict=True in a scripted recipe to turn both into an error instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYes
baseYes
toolYes
strictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the sparse annotations: explains the conditional `warnings` key, sign convention for removed_volume, None volume_ratio, and the two degenerate-cut cases. Also discloses strict-mode behavior and default warn-don't-fail, so side effects are fully predictable.

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?

Long but tightly organized: purpose, params, return semantics, then edge cases. Every sentence earns its place, and the warnings-key test is stated operationally.

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

Completeness5/5

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

With no output schema, the description supplies return fields and units, conditional keys, and failure semantics. An agent has everything needed to call boolean_op and interpret its result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates: it defines the three valid op values, clarifies base/tool provenance, and explains strict's default and effect. This is more parameter guidance than most schemas provide.

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 and resource: 'Boolean operation on two existing objects, referenced by their handles.' It enumerates cut/fuse/common, so an agent can distinguish it from other geometry transforms and feature tools in the sibling list.

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

Usage Guidelines4/5

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

Describes the operating modes and says base/tool are handles returned from add_primitive, giving clear usage context. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of 5.

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