Skip to main content
Glama

daz_interactive_pose

Position two characters for interactive poses like hugging, facing each other, shoulder arm, or handshake with adjustable distance.

Instructions

Coordinate two characters for interactive poses.

Applies complementary poses to two characters for common interaction scenarios. Handles both positioning and pose application.

Args: char1_label: Display label of first character. char2_label: Display label of second character. interaction_type: Type of interaction. Options: - "face-each-other": Position and rotate to face each other (default) - "hug": Both characters hug with arms around each other - "shoulder-arm": Char1 puts arm around char2's shoulders - "handshake": Both extend right hands for handshake distance: Optional spacing between characters in cm (default varies by type: face=100, hug=40, shoulder-arm=30, handshake=60).

Returns:

  • success: true on success

  • char1: first character label

  • char2: second character label

  • interactionType: the interaction type used

  • applied: list of pose components that were applied

Example: # Position characters facing each other at conversation distance daz_interactive_pose("Alice", "Bob", "face-each-other", distance=120)

# Create tight hug
daz_interactive_pose("Alice", "Bob", "hug", distance=30)

# Bob puts arm around Alice's shoulders
daz_interactive_pose("Bob", "Alice", "shoulder-arm")

Note: These are simplified interaction poses. For natural-looking results, you may need to fine-tune positions and rotations using daz_set_property or load artist-created pose presets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
char1_labelYes
char2_labelYes
interaction_typeNoface-each-other
distanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description fully carries the burden of disclosing behavior. It states that the tool applies complementary poses and positioning, returns success, labels, and applied pose components. It also mentions that distances vary by interaction type. However, it does not explicitly state whether poses override existing ones, though the note implies they are simplified and may need adjustment.

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

Conciseness4/5

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

The description is well-structured with a clear purpose statement, parameter details, returns, examples, and a note. It is somewhat lengthy but every sentence adds value. Minor redundancy in the returns section could be trimmed, but overall it is effective.

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

Completeness5/5

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

Given the presence of an output schema, the description goes beyond by including return values, examples, and caveats. It covers the tool's core functionality, parameters, and limitations, providing all necessary information for an AI agent to use it correctly.

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

Parameters5/5

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

The input schema has 0% description coverage, but the tool description compensates completely by explaining each parameter: char1_label and char2_label as display labels, interaction_type with a list of options and defaults, and distance with type-specific default values. Examples further clarify usage.

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 the tool coordinates two characters for interactive poses, specifying that it handles both positioning and pose application. It distinguishes itself from siblings by focusing on paired interactions, with no other sibling tool having a similar function.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool and when alternatives are needed. It lists interaction types with defaults, includes detailed examples, and notes that for natural-looking results, fine-tuning with daz_set_property or artist-created pose presets may be required.

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