Skip to main content
Glama

daz_load_camera_preset

Restore camera position and rotation from a saved preset. Apply preset data to any camera to replicate camera setups across scenes.

Instructions

Restore camera position and rotation from preset data.

Applies saved preset data (from daz_save_camera_preset()) to a camera, restoring its position, rotation, and scale.

Args: camera_label: Display label of the camera to modify. preset: Preset dictionary from daz_save_camera_preset(), containing: - transforms: Dictionary of property names to values

Returns:

  • success: true on success

  • camera: camera label

  • applied: list of property names that were applied

Example: # Load previously saved preset with open("my_camera_preset.json") as f: preset = json.load(f)

result = daz_load_camera_preset("Camera 1", preset["preset"])
print(f"Applied properties: {result['applied']}")

# Apply same preset to multiple cameras
cameras = ["Camera 1", "Camera 2", "Camera 3"]
for cam in cameras:
    daz_load_camera_preset(cam, preset["preset"])

Note: - Preset can be applied to any camera, not just the original - Only properties present in the preset are modified - Useful for saving/loading camera positions across sessions - Can be used to synchronize multiple cameras

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camera_labelYes
presetYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, but the description covers what the tool does (restore position, rotation, scale), what is modified (only properties present in preset), return values, and application to any camera. This is comprehensive.

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?

Well-structured with sections (Args, Returns, Example, Note). Every sentence adds value, though slightly lengthy for a simple function. Front-loaded with purpose.

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 two parameters, no annotations, and presence of output schema, the description covers functionality, parameters, return, and examples. Lacks error handling details but is sufficient for this tool.

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?

With 0% schema coverage, the description adds crucial meaning: 'camera_label' is the display label, 'preset' is a dictionary containing transforms. This fully compensates for the sparse 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 'Restore camera position and rotation from preset data' with a specific verb and resource. It distinguishes from siblings like daz_save_camera_preset by focusing on loading/applying presets.

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?

Provides clear context and examples, including applying to multiple cameras and reloading across sessions. However, it does not explicitly exclude scenarios or compare to daz_apply_camera_angle, leaving some ambiguity.

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