Skip to main content
Glama

create_array_of_objects

Duplicate an object into an array by setting count and offset to generate repeated geometry for modeling tasks.

Instructions

Duplicate an object into an array along an offset.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
countNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden. 'Duplicate' implies new objects are created in the scene, but the description never states whether the source object is preserved, whether the copies are linked or independent, whether a new collection is made, or what side effects occur — significant gaps for a scene-mutating tool.

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

Conciseness3/5

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

A single short sentence with no wasted words and the core action front-loaded. But the brevity is under-specification rather than economy, leaving too little for a three-parameter tool.

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?

An output schema exists, so return values need not be described, but for a tool with three undocumented parameters and no annotations the description should still cover parameter meaning and creation side effects. It does neither, leaving the definition materially incomplete.

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% and the description only echoes 'offset' and, implicitly, the array/count idea. It does not explain that 'count' controls the number of duplicates (default 3) or that 'offset' is a per-axis numeric vector, both of which the agent must guess from bare titles.

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 gives a verb ('Duplicate') and a resource ('an object') plus the resulting shape ('an array along an offset'), so the general intent is graspable. However, it does not discriminate this tool from nearby creation tools like create_object or create_hierarchy, and the phrase 'array along an offset' is ambiguous about whether copies are positioned along a vector or a path.

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 mention of alternatives such as creating objects individually or duplicating via other tools, and no stated preconditions (e.g. whether an object must be selected or named explicitly). The agent must infer all routing decisions from the name alone.

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