Skip to main content
Glama

create_object

Creates a 3D object of a specified type, optionally setting its name, location, rotation, scale, and collection.

Instructions

Create a generic object by type.

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": {
      "object_type": "<object_type>"
    },
    "name": "create_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
scaleNo
locationNo
rotationNo
collectionNo
object_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/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 for a mutation tool. It does not disclose side effects, whether the object is added to the active scene or collection, how defaults are applied, permission requirements, or what happens when optional transform parameters are omitted.

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 description is a single short sentence with no wasted wording, but it is under-specified rather than appropriately concise. For a six-parameter creation tool with many siblings, five words are not enough to structure the necessary information.

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?

The output schema exists, so return values need not be explained, but the tool is a mutation with no annotations and six undocumented parameters. The description provides almost nothing to help an agent understand valid object types, parameter effects, or creation behavior in a crowded sibling set.

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 six parameters, and the description only indirectly references the required object_type via 'by type'. It adds no meaning for name, scale, location, rotation, or collection, leaving most parameters undocumented in both schema and description.

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?

The description states a specific verb and resource: creating a generic object by type. However, it does not clarify what an 'object' is here, what valid object types exist, or how this differs from the many specific creation siblings such as create_cube or create_empty. The purpose is understandable but leaves meaningful ambiguity.

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 guidance on when to use this generic creation tool instead of a specialized sibling like create_cube, create_cone, or create_empty. The word 'generic' weakly implies broader applicability, but no explicit conditions or alternatives are given.

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