Skip to main content
Glama
sosadly
by sosadly

add_cube

Add a cube to a Blockbench model with from-to coordinates. Supports single-axis rotation and inflate for rounding. Returns cube uuid and face UVs for painting.

Instructions

Add a cube to the model. Coordinates are in Blockbench units. Cubes support rotation (degrees) and inflate (round/shrink without moving) — use them; flat axis-aligned boxes look robotic. For compound multi-axis angles, parent the cube to a rotated group instead. Prefer add_cubes to build many cubes at once. Returns the created cube with uuid and resolved face UVs (paint onto those with paint_faces).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesUpper corner [x,y,z].
fromYesLower corner [x,y,z].
nameNo
facesNoOptional per-face setup, keyed by north/south/east/west/up/down. Each: {uv:[x1,y1,x2,y2], rotation, texture: name|uuid}.
autouvNo0 disabled, 1 auto, 2 relative auto.
box_uvNoUse box UV (default follows the format).
originNoRotation pivot [x,y,z] (defaults to `from`).
parentNouuid or name of the parent group.
inflateNoInflate (+) or shrink (-) all faces in place — use for rounding/taper.
rotationNoRotation in degrees [x,y,z]. Single-axis is most reliable per cube.
uv_offsetNo[u,v] offset for box UV.
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses return values (uuid, resolved UVs), coordinate system (Blockbench units), and supported features (rotation, inflate). It does not mention permissions or side effects, but the behavior is clear for a non-destructive create operation.

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?

Five front-loaded sentences with no wasted words. Each sentence adds critical context: purpose, coordinates, feature recommendations, alternative usage, and return value. Highly efficient.

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?

Despite no output schema, the description covers return values and links to painting. It mentions key optional features and provides enough context for a modeling tool. All important aspects are addressed given the tool's complexity.

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 coverage is 91% (high), baseline 3. The description adds value by explaining coordinate units, defaults (origin to from), and usage hints for rotation and inflate. This goes beyond the schema definitions.

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?

The description clearly states 'Add a cube to the model' and distinguishes it from siblings by recommending 'add_cubes' for batch adding. It specifies the resource (cube) and the action (add), with no ambiguity.

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?

The description provides explicit guidance: prefer add_cubes for many cubes, parent to a rotated group for compound angles, and use rotation/inflate to avoid robotic flat boxes. It tells when and why to use this tool vs alternatives.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sosadly/blockbench-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server