Skip to main content
Glama

daz_save_camera_preset

Captures camera position, rotation, and scale as a serializable preset dictionary for later restoration with the load camera preset tool.

Instructions

Save camera position and rotation as preset data.

Captures the current transform properties of a camera (position, rotation, scale) and returns them as preset data. This data can be saved by the client and later restored using daz_load_camera_preset().

Args: camera_label: Display label of the camera to save.

Returns:

  • preset: Dictionary containing:

    • label: camera label

    • transforms: Dictionary of property names to values (XTranslate, YTranslate, ZTranslate, XRotate, YRotate, ZRotate, XScale, YScale, ZScale)

Example: # Save camera position preset = daz_save_camera_preset("Camera 1")

# Client can store preset data (e.g., in a file or database)
import json
with open("my_camera_preset.json", "w") as f:
    json.dump(preset, f)

# Later, restore the camera
with open("my_camera_preset.json") as f:
    preset = json.load(f)
daz_load_camera_preset("Camera 1", preset["preset"])

Note: - Preset data is a plain dictionary that can be serialized (JSON, etc.) - Includes all transform properties (position, rotation, scale) - Does not include camera-specific settings (focal length, DOF, etc.) - Preset data can be applied to any camera, not just the original

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camera_labelYes

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 description thoroughly discloses behavior: captures current transform properties (read operation), returns serializable dictionary, lists included/excluded properties, and notes applicability to any camera. No contradictions.

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 summary, parameter, return, example, and notes. However, the example is somewhat verbose (including JSON file handling), which could be trimmed without losing clarity.

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 simplicity (1 parameter, output schema described), the description is fully complete: explains purpose, input, output format, usage pattern, limitations, and provides a practical example. No gaps.

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 has 0% coverage, but description adds semantic meaning: 'camera_label' is described as 'Display label of the camera to save', clarifying that it is a human-readable label, not an internal ID.

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?

Description clearly states the verb 'save' and resource 'camera preset data', and explicitly distinguishes from sibling tool 'daz_load_camera_preset' by mentioning its counterpart and usage pattern.

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 usage context: capturing and restoring camera transforms via serialization, with example. Notes what is excluded (camera-specific settings) but does not explicitly name alternative tools for those settings.

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