Skip to main content
Glama
rokibul-mist

rhino-mcp

by rokibul-mist

rhino_cmd_boolean_difference

Subtract selected cutter objects from base objects in Rhino. Optionally delete the cutter objects after the operation.

Instructions

    Boolean difference: subtract selected cutters from base objects.
    
    Args:
    controller: RhinoController instance.
    delete_input: Delete input cutter objects after the operation.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delete_inputNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

The description only mentions the subtract action and the delete_input parameter's effect; it doesn't disclose other side effects like potential modification of base objects or undo behavior. With no annotations, the minimal description leaves significant behavioral ambiguity.

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?

The description is exceptionally concise, using one clear sentence for the purpose and brief parameter descriptions. No unnecessary words or redundancy are present.

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

Completeness2/5

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

Critical context is missing: there is no description of return values or success indicators, no details on how objects are selected, and no comparison with sibling boolean tools. This makes it hard for an agent to know if the operation succeeded or what to expect.

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?

The delete_input parameter is clearly described as deleting input objects after the operation, and the controller parameter is mentioned in the text. However, the controller is not present in the provided input schema, and the description doesn't explain how it influences the operation or its default behavior.

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 clearly states the operation is a boolean difference that subtracts cutters from base objects, which is a specific verb and resource. However, it doesn't explicitly distinguish this command from the sibling rhino_boolean_difference function, so the 'cmd' nature is implied but not clarified.

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

Usage Guidelines1/5

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

No usage guidance is provided. It doesn't explain when to use this command versus the similar rhino_boolean_difference tool, nor does it mention prerequisites like object selection or how cutters/base objects are identified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools