Creates multiple mesh objects in Blender in a single call by defining each object's type, name, location, and scale, simplifying scene setup.
Create multiple objects in one call.
Each object: {"type": "MESH", "name": "Obj", "location": [x,y,z], "scale": [sx,sy,sz]}
Args: objects: List of object definitions.
| Name | Required | Description | Default |
|---|---|---|---|
| objects | Yes |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It provides a sample object structure but does not disclose side effects, failure behavior, atomicity, required fields, or limits. It only states the basic mutation without details on how the operation behaves under error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured: a one-line purpose, a sample object, and an args list. No unnecessary filler. It could be slightly more compact, but it is efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool creates multiple objects with no annotations, output schema, or detailed parameter schema, the description is insufficient. It lacks information about required fields, defaults, error handling, return values, or interaction with other tools. The agent may not know how to construct valid objects or handle failures.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% (schema has no descriptions and uses additionalProperties true). The description adds a concrete example of the expected object structure (type, name, location, scale), which is helpful. However, it does not specify which fields are required or all possible types, so it partially compensates but is incomplete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Create multiple objects in one call', which is a clear verb+resource and implies a batch operation distinct from single-object tools like create_object. It does not explicitly contrast with sibling batch tools, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. It does not mention 'use for bulk creation' or differentiate from create_object or other batch tools like batch_transform or batch_parent. The agent must infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.