Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

camera_set

Adjust an existing Daz Studio camera's position, aim, framing, or active state; optionally fit scene labels or set focal length for the shot.

Instructions

Moves, aims or reframes an existing camera, or makes it the active one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "camera": "<camera>"
    },
    "name": "camera_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
yawNo
frameNoLabels to fit in the picture.
labelNoNew label.
pitchNo
cameraYesCamera label.
marginNo
look_atNo
positionNo
rotationNo
make_activeNo
focal_lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation. The description adds useful context that it operates on an existing camera and can make it active, but it omits failure behavior when the camera does not exist, persistence/undo details, and side effects of changing the active camera.

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 a single front-loaded sentence with no filler and clear action grouping. It is structurally efficient, though its brevity leaves important parameter details unstated.

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

Completeness2/5

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

For an 11-parameter mutation tool with low schema description coverage and no output schema, the definition is under-specified. It does not explain parameter interactions, coordinate conventions, failure modes, or what happens when 'make_active' changes scene state.

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

Parameters2/5

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

The schema has 11 parameters but only 27% description coverage, so the description must carry more explanatory weight. It broadly maps 'moves', 'aims', 'reframes', and 'makes active' to some actions, but does not explain yaw, pitch, margin, position, rotation, focal_length, label, units, defaults, or coordinate behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb set and resource: moving, aiming, reframing, or activating an existing camera. 'Existing camera' partially distinguishes it from camera_create, though it does not explicitly differentiate from camera_shot or other camera siblings.

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 phrase 'existing camera' implies this is for modifying a camera that already exists, not creating one, which gives some usage context. However, it does not explicitly say when to use this instead of camera_create or camera_shot, nor does it describe prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools