Skip to main content
Glama

create_primitive

Creates a mesh primitive such as a cube, sphere, or cylinder in Blender with configurable size, scale, location, rotation, smoothing, and collection.

Instructions

Create a mesh primitive (cube, uv_sphere, cylinder, ...).

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": "<primitive>"
    },
    "name": "create_primitive"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
sizeNo
scaleNo
smoothNo
locationNo
rotationNo
primitiveYes
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say where the primitive is placed (which collection if `collection` is omitted), whether the object is linked into the scene, whether it becomes selected/active, or what defaults apply for size and smooth.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but the brevity reflects under-specification rather than disciplined editing.

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?

For an 8-parameter mutation tool with zero annotations and zero schema descriptions, one sentence is far too thin. The presence of an output schema excuses explaining return values, but placement, units for size/location/rotation, and the primitive/value vocabulary all remain undocumented.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the raw schema gives only names and types. The description only implies valid values for `primitive` via examples (cube, uv_sphere, cylinder) and adds nothing about `size`, `scale`, `smooth`, `location`, `rotation`, or `collection`. It fails to compensate for the near-total documentation gap.

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 mesh primitive" states a specific verb and resource, and the parenthetical examples (cube, uv_sphere, cylinder) make the output concrete. It stops short of distinguishing this tool from siblings like create_cube, create_uv_sphere, or create_cylinder, which produce exactly the same objects, so the boundary is left ambiguous.

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, no statement of when this generic entry point should be preferred over the dedicated create_cube / create_sphere / create_torus siblings, and no prerequisites mentioned. The agent must guess whether create_primitive or a named sibling is the intended call.

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