Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

camera_create

Adds a camera to a Daz Studio scene, either automatically framing specified nodes in the shot or placing it at a set position aimed at a target point.

Instructions

Adds a camera, either framing nodes automatically or at a position aimed at a target.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "camera_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
yawNoWith frame: degrees around them; 0 = in front, 90 = their left, -90 = their right.
frameNoLabels to fit in the picture, e.g. both figures. Places and aims the camera.
labelNoCamera
pitchNoWith frame: degrees above their center.
marginNoWith frame: 1.1 leaves 10 % of room.
look_atNo
positionNo[x, y, z] cm.
rotationNo[x, y, z] degrees when not aiming.
make_activeNoLook through it (captures and renders use it).
focal_lengthNomm; 35 wide, 65 default, 85-135 portraits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this is a non-destructive mutation in a closed scene. The description adds little beyond that: it does not say whether existing cameras are overwritten, whether the new camera becomes the active view by default, or how conflicting mode parameters are resolved. With annotations covering the safety profile, this is an acceptable but thin addition.

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?

One front-loaded sentence with zero waste, and the two-mode structure is established immediately. It errs on the terse side, leaving nothing superfluous but also little scaffolding for a ten-parameter tool.

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 a tool with ten parameters, all optional, split into mutually exclusive clusters, the description does not explain how the clusters interact or what the call returns (for example whether a label for the created camera is produced). No output schema exists to fill that gap. With annotations and an 80%-covered schema, the remaining critical gap is mode precedence, which the description should have addressed.

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

Parameters3/5

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

Schema description coverage is 80%, so the schema already explains yaw, pitch, margin, focal_length, and make_active. The description contributes the conceptual grouping of parameters into a framing cluster versus a placement cluster, which helps navigate ten optional parameters, but it does not clarify precedence when both frame and position/look_at are supplied. Baseline 3 is appropriate.

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 uses a specific verb and resource ("Adds a camera") and names the two operating modes: automatic framing of nodes versus explicit placement aimed at a target. It does not distinguish the tool from siblings such as camera_set or camera_shot, so an agent must infer the boundary from names alone.

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 single sentence implies when each mode applies (pass frame targets to auto-frame, otherwise position at a target), which is usable guidance. However, it never states when to use this versus camera_set or camera_shot, nor any prerequisites, so the agent must guess at the alternative.

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