Skip to main content
Glama

create_cube

Create a cube in Blender with configurable size, location, name, and collection for 3D modeling and scene setup.

Instructions

Create a cube.

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": "create_cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
sizeNo
locationNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies mutation through the word "Create". It says nothing about defaults in effect (size defaults to 2), the coordinate system or units for location, whether the object is added to the active collection, selection state afterward, or any undo/permission behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short but that is under-specification rather than conciseness, matching the pattern where brevity comes at the cost of missing information. There is nothing to front-load and no wasted wording, but the single phrase does not earn its place as a definition.

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?

An output schema exists, so return values need not be explained, but with four optional parameters at 0% schema description coverage and no annotations, the definition leaves the agent without enough to call the tool correctly (units, coordinate frame, target collection). For a scene-mutating creation tool, this is a substantial gap.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (name, size, location, collection), and the description adds no meaning to any of them. Units for size, the expected three-element format and reference frame for location, and the semantics of collection are all left completely undocumented.

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

Purpose3/5

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

"Create a cube" names a concrete verb and resource, so the agent knows this produces cube geometry rather than a sphere or camera. But it is essentially a restatement of the tool name with no further scope detail, and it does nothing to distinguish itself from the large set of adjacent primitive-creation siblings beyond the noun "cube".

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when a cube is preferable to create_primitive, create_mesh, or add_modifier, and no prerequisites such as whether a scene or collection must exist first. The agent must infer usage from the name alone.

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