Skip to main content
Glama

create_empty

Creates an empty object in Blender with optional name, location, collection, and display type to serve as a transform or reference point.

Instructions

Create an empty.

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_empty"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
locationNo
collectionNo
empty_display_typeNoPLAIN_AXES

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/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, yet it says nothing about whether the new empty is linked into the scene, what the defaults produce, or whether the operation is reversible. A single tautological phrase leaves mutation behavior entirely opaque.

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 single sentence is short but that brevity reflects under-specification rather than economy — there is nothing front-loaded because there is essentially nothing stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four undocumented optional parameters, no annotations, and a domain-specific object type, this definition is far too thin. The existing output schema removes the need to document return values, but nothing else about invoking the tool is covered.

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, location, collection, empty_display_type), and the description adds no meaning for any of them. Notably, the distinction between 'collection' (a parent collection name?) and 'location' (a coordinate array?) is left completely unexplained.

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

Purpose2/5

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

"Create an empty" is essentially the tool name restated as a sentence. It does not explain what an "empty" is in this domain (a transform-only scene object) or how it differs from the many other create_* siblings such as create_object or create_collection.

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

Usage Guidelines1/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 prerequisites, and no mention of any alternative among the ~30 sibling creation tools. An agent has no basis for choosing create_empty over create_object or create_collection.

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