Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_object

Add a primitive object such as a cube, sphere, or cylinder to the current Blender scene with optional name, position, rotation, and scale.

Instructions

Create a primitive object in the scene.

Args: type: Primitive type. One of: CUBE, SPHERE, UV_SPHERE, ICO_SPHERE, CYLINDER, CONE, TORUS, PLANE, CIRCLE, MONKEY, EMPTY. name: Optional name for the object. Auto-generated if empty. location: XYZ position as a 3-element list/tuple. Defaults to origin. rotation: XYZ Euler rotation in radians as a 3-element list/tuple. scale: XYZ scale as a 3-element list/tuple. Defaults to (1,1,1).

Returns: Dict with the created object's name, type, and location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
typeYes
scaleNo
locationNo
rotationNo

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 / type / enum
      Added value: +[
+  "CIRCLE",
+  "CONE",
+  "CUBE",
+  "CYLINDER",
+  "EMPTY",
+  "ICO_SPHERE",
+  "MONKEY",
+  "PLANE",
+  "SPHERE",
+  "TORUS",
+  "UV_SPHERE"
+]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/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. It does disclose useful traits: name is auto-generated when empty, and each transform parameter has a default. However, it says nothing about where the object lands (active collection?), whether it becomes selected/active, error behavior on invalid enums, or whether the operation is undoable.

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?

Front-loaded one-line purpose followed by compact Args/Returns blocks. The enum listing is slightly redundant with the schema but keeps the description self-contained, and no sentence is wasted.

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?

An output schema exists, so the Returns section is somewhat redundant, though harmless. For a 5-param mutation tool with no annotations, the description is nearly complete; only the side effects of creation (selection state, target collection) are unaddressed.

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%, so the description must compensate, and it does: it gives units for rotation (radians), the required shape/format for vector params ('3-element list/tuple'), defaults for location and scale, and the meaning of an empty name. This adds real meaning beyond the bare schema types.

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 ('Create a primitive object in the scene') and the 'primitive' qualifier distinguishes it from sibling creators like create_text, create_curve, create_armature, or create_polygon_prism. An agent can identify this as the entry point for adding generator-based primitives without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the name and description (this is the tool for adding a primitive), but there is no explicit when/when-not guidance and no sibling is named. With dozens of create_* siblings in the list, a sentence like 'use create_text/create_curve for non-primitive geometry' would have materially helped routing.

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