Skip to main content
Glama

daz_orbit_camera_around

Positions camera around a target node at specified angles and distance, then automatically aims at the target. Sets viewpoints like bird's-eye, low angle, or side views.

Instructions

Position camera orbiting around a target node at specified angle and distance.

Uses spherical coordinates to position the camera at a specific angle around a target object. The camera is automatically aimed at the target after positioning.

Args: camera_label: Display label of the camera to position. target_label: Display label of the target node to orbit around. distance: Distance from target in centimeters (default: 200). angle_horizontal: Horizontal angle in degrees, 0=front/+Z, 90=right/+X (default: 45). angle_vertical: Vertical angle in degrees, positive=above, negative=below (default: 15).

Returns:

  • success: true on success

  • camera: camera label

  • target: target node label

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

  • targetPosition: target world position {x, y, z}

Example: # Position camera at 45° to the right, slightly above, 200cm away daz_orbit_camera_around("Camera 1", "Genesis 9", distance=200, angle_horizontal=45, angle_vertical=15)

# Side view from the left
daz_orbit_camera_around("Camera 1", "Genesis 9", distance=150,
                        angle_horizontal=-90, angle_vertical=0)

# Bird's eye view
daz_orbit_camera_around("Camera 1", "Genesis 9", distance=300,
                        angle_horizontal=0, angle_vertical=60)

# Dramatic low angle
daz_orbit_camera_around("Camera 1", "Genesis 9", distance=180,
                        angle_horizontal=25, angle_vertical=-20)

Note: Angles use spherical coordinates: - Horizontal: 0°=front(+Z), 90°=right(+X), 180°=back(-Z), -90°=left(-X) - Vertical: positive=above horizon, negative=below

Camera is automatically aimed at the target's world position after positioning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camera_labelYes
target_labelYes
distanceNo
angle_horizontalNo
angle_verticalNo

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, the description carries full burden. It discloses that the camera is automatically aimed at the target after positioning, explains the spherical coordinate system, and provides defaults. It does not mention side effects like overwriting camera orientation or requiring camera label existence, but covers key behavioral aspects.

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 summary, args, returns, examples, and notes. It is front-loaded with purpose. However, the four examples are somewhat verbose; two would suffice, but they are still helpful.

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 complexity (5 parameters, spherical coordinates, automatic aiming), the description is complete. It explains parameter behavior, coordinate system, return values, and provides usage examples. No output schema is needed as returns are fully documented.

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?

Schema coverage is 0%, so the description must compensate. It provides detailed parameter semantics including defaults, coordinate definitions, and explanations for all five parameters. Examples illustrate usage and coordinate interpretation, adding significant 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 function: 'Position camera orbiting around a target node at specified angle and distance.' It uses specific verbs (position, orbiting) and identifies the resources (camera, target node). It distinguishes from sibling tools like daz_frame_camera_to_node and daz_look_at_character by focusing on spherical coordinate positioning.

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

Usage Guidelines3/5

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

The description implies usage for camera positioning around targets but does not explicitly state when to use this tool vs alternatives. No exclusions or when-not-to-use guidance is provided, leaving the agent to infer context.

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