Skip to main content
Glama

daz_batch_transform

Batch apply translate, rotate, and scale transforms to multiple nodes simultaneously for uniform scene adjustments.

Instructions

Apply the same transform properties to multiple nodes.

Useful for moving, rotating, or scaling multiple objects by the same amount. Only properties that exist on each node are applied (missing properties are silently skipped).

Args: node_labels: List of node display labels to transform. transforms: Dictionary of property names to values (e.g., {"XTranslate": 50, "YRotate": 45}).

Returns:

  • results: Array of result objects with success, node, applied properties, error

  • successCount: Number of nodes successfully transformed

  • failureCount: Number of nodes that failed

  • total: Total number of nodes attempted

Example: # Move multiple props to the right daz_batch_transform( ["Prop1", "Prop2", "Prop3"], {"XTranslate": 100} )

# Rotate and scale multiple objects
daz_batch_transform(
    ["Chair", "Table", "Lamp"],
    {"YRotate": 45, "Scale": 1.2}
)

# Reset rotation for all cameras
daz_batch_transform(
    ["Camera 1", "Camera 2", "Camera 3"],
    {"XRotate": 0, "YRotate": 0, "ZRotate": 0}
)

Note: Transform properties include: XTranslate, YTranslate, ZTranslate, XRotate, YRotate, ZRotate, Scale, XScale, YScale, ZScale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_labelsYes
transformsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided. Description adds behavioral context: missing properties are silently skipped, and return structure is detailed. However, it doesn't mention permissions, reversibility, or other side effects. With no annotations, description carries full burden but is adequate.

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

Conciseness5/5

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

Well-structured with Args, Returns, Example, and Note sections. Front-loaded with purpose. Each sentence serves a purpose; no fluff.

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

Completeness4/5

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

Given 2 parameters and existence of output schema, description covers operation, fallback behavior (silent skip), return structure, and examples. Missing error handling details, but output schema likely covers that. Sufficient for a batch tool.

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

Parameters4/5

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

Schema description coverage is 0%, so description must compensate. It explains node_labels as 'list of node display labels' and transforms as 'dictionary of property names to values', with a list of valid transform properties and examples. This adds significant meaning beyond the raw schema.

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

Purpose5/5

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

The description clearly states it applies the same transform properties to multiple nodes. Examples and list of transform properties further clarify. It distinguishes from siblings like daz_batch_set_properties (sets arbitrary properties) and daz_batch_select (selects nodes).

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Useful for moving, rotating, or scaling multiple objects by the same amount.' This provides clear context, but it doesn't explicitly contrast with alternatives (e.g., daz_set_property for single node) or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bluemoonfoundry/daz-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server