Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_primitive

Creates a validated cube, sphere, cylinder, or plane in the active Blender scene with explicit user approval, preventing name collisions and preserving existing objects.

Instructions

Create a validated basic 3D primitive (cube, sphere, cylinder, plane) in the active Blender scene. Requires explicit user approval through a trusted approval mechanism to authorize scene modification. Client- or model-supplied approval flags in tool arguments are untrusted and cannot authorize mutations. Validates input geometry, prevents name collisions, and preserves existing scene objects.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "primitive_type": "<primitive_type>",
      "name": "<name>"
    },
    "name": "create_primitive"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name for the new object. Must not collide with any existing object.
sizeNoEdge length in Blender units for plane primitive. Must be positive (0.0001 to 10000.0). Applies only to 'plane' (default 1.0).
depthNoHeight/depth in Blender units for cylinder primitive. Must be positive (0.0001 to 10000.0). Applies only to 'cylinder' (default 1.0).
radiusNoRadius in Blender units for sphere or cylinder primitive. Must be positive (0.0001 to 10000.0). Applies to 'sphere' (default 0.5) and 'cylinder' (default 0.5).
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
locationNo3D world coordinates [x, y, z] for object placement.
segmentsNoNumber of vertical segments for UV sphere. Range: 3 to 500. Applies only to 'sphere' (default 32).
verticesNoNumber of circular vertices for cylinder cross-section. Range: 3 to 500. Applies only to 'cylinder' (default 32).
dimensionsNoSize dimensions [x, y, z] in Blender units. Must be non-negative numbers. Optional; defaults to match primitive geometry.
ring_countNoNumber of horizontal rings for UV sphere. Range: 3 to 500. Applies only to 'sphere' (default 16).
primitive_typeYesType of 3D primitive to create. Supported: 'cube', 'sphere', 'cylinder', 'plane', 'cone', 'torus', 'monkey', 'grid'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the approval gate, explicitly warns that client/model-supplied approval flags in arguments are untrusted, and states that geometry is validated, name collisions are prevented, and existing objects are preserved. It does not cover atomicity/rollback, what error or object is returned on success (no output schema exists), or how approval is actually obtained — gaps a mutation tool would ideally close.

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

Conciseness4/5

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

Four sentences, front-loaded with the action, then the safety constraint, then the validation guarantees — no filler or narrative. Slight redundancy between the approval sentence and the untrusted-flags sentence, but that repetition is defensible for a security-critical constraint.

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?

For a twelve-parameter mutation tool with no annotations and no output schema, the description covers the two things structured fields cannot: the approval gate and the non-destructive validation/collision-preservation behavior. The residual gap is that nothing describes what a successful or failed call yields, and the type list disagrees with the enum, which matters because per-type parameters silently apply only to some primitives.

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 description coverage is 100%, so per-parameter meanings, ranges, and per-primitive applicability are already documented; baseline is 3. The description adds cross-parameter value by naming the collision rule on the required 'name' field and by framing the whole call as validated input geometry. It is capped short of 5 because it adds no semantics for the type-specific parameters beyond repeating what the schema says.

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?

"Create a validated basic 3D primitive ... in the active Blender scene" is a specific verb plus resource, and the parenthetical names concrete shapes. However the parenthetical lists only cube/sphere/cylinder/plane while the schema enum supports eight types (cone, torus, monkey, grid), so the stated scope under-describes what the tool actually accepts.

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?

The description establishes a clear precondition (trusted user approval required for scene mutation) and implies use in the active scene, which is real guidance. It offers no explicit when-to-use/when-not-to-use guidance against alternatives such as create_curve, create_camera, or other create_* siblings — an agent gets no routing signal beyond 'this makes primitives'. If the tool silently fails without approval, the caller is at least warned, but not told what to do instead when approval is unavailable.

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