Skip to main content
Glama

daz_frame_camera_to_node

Positions the camera to frame a specified node in the scene, automatically calculating distance based on the node's bounding box or using a user-defined distance.

Instructions

Frame camera to show a node by positioning at calculated distance.

Positions the camera to frame the specified node in view. Calculates the node's bounding box and positions the camera at an appropriate distance to show the entire object. Camera is positioned in front (+Z) and aimed at the node's center.

Args: camera_label: Display label of the camera to position. node_label: Display label of the node to frame. distance: Optional distance from node center in cm. If not specified, calculated as 2.5x the largest dimension of the node's bounding box.

Returns:

  • success: true on success

  • camera: camera label

  • node: node label

  • position: camera world position {x, y, z}

  • nodeCenter: node bounding box center {x, y, z}

  • nodeSize: node bounding box size {x, y, z}

Example: # Frame a character (auto distance) daz_frame_camera_to_node("Camera 1", "Genesis 9")

# Frame a prop with specific distance
daz_frame_camera_to_node("Camera 1", "Sword", distance=50)

# Frame entire scene
daz_frame_camera_to_node("Camera 1", "Scene", distance=500)

# Close-up on head
daz_frame_camera_to_node("Camera 1", "head", distance=30)

Note: - Auto-calculated distance is 2.5x the largest bounding box dimension - Camera is positioned in front of the node (+Z direction) - Camera is aimed at the center of the node's bounding box - Useful for automatically framing objects of varying sizes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camera_labelYes
node_labelYes
distanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries full burden and excels: it explains the camera is positioned in front (+Z), aimed at the center, and calculates distance as 2.5x the largest bounding box dimension. It also details the return values (position, nodeCenter, nodeSize). This is comprehensive behavioral disclosure.

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?

The description is well-structured: summary sentence, detailed explanation, parameter list, return values, examples, and notes. Every sentence serves a purpose, and the information is front-loaded efficiently.

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 tool's simplicity (3 parameters, 2 required) and the presence of an output schema (though not shown), the description is complete. It explains behavior, parameters, return values, and provides multiple examples covering common use cases.

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 lacks descriptions (0% coverage), but the description fully compensates: it explains camera_label and node_label as display labels, and distance as optional with auto-calculation formula (2.5x largest dimension). This adds critical meaning beyond the 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 the tool's purpose: 'Frame camera to show a node by positioning at calculated distance.' It specifies the verb (frame), resource (camera and node), and distinguishes from sibling tools like daz_orbit_camera_around or daz_set_active_camera by focusing on framing a specific node in view.

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?

The description provides usage context with examples and a note, indicating when to use auto-distance vs manual distance. However, it does not explicitly compare to sibling tools or state when not to use this tool, which would elevate clarity further.

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