Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

content_load

Adds figures, props, clothing, hair, poses, characters, shapes, or materials to a Daz Studio scene, applying presets to a target node and returning the new scene nodes.

Instructions

Loads content into the scene: adds a figure or prop, dresses a figure (clothing, hair), applies a pose, character, shape or material preset to the target. Returns the new nodes.

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": {
      "path": "<path>"
    },
    "name": "content_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesContent file from content_search (absolute, or relative to a library such as 'People/Genesis 9/Genesis 9.duf').
targetNoLabel of the node it applies to. Required for clothing, hair, poses, characters, shapes and materials; omit for figures, props and lights.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/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, non-open-world operation, so the mutation profile is known. The description adds that it returns the new nodes, which is genuinely useful return-value context. It says nothing about permission needs, undo/rollback, or what happens on a failed fit, which is the remaining gap for a scene-mutating tool.

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?

A single front-loaded sentence: the core action first, then the enumerated cases, then the return value. No filler wording. The mid-sentence list is dense but each item adds information rather than repeating the schema.

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?

For a 2-parameter, fully-described, non-destructive load operation, the description covers what it does, what it affects, and what it returns. With no output schema, the 'Returns the new nodes' clause fills that gap. Only edge-case behavior (failure, partial application) is absent.

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 coverage is 100%, so both parameters (path, target) are already fully documented, including the target-required-per-content-type rule. The description reinforces the target semantics with 'to the target' but adds no format, path-resolution, or failure-mode detail beyond the schema. Baseline 3 applies.

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?

States a specific verb ('Loads content into the scene') and then enumerates the concrete operations: adding figures/props, dressing figures, and applying pose/character/shape/material presets. An agent can picture the effect without opening the schema. It stops short of naming which sibling to use for related-but-different tasks (e.g. content_add_library, content_search), so it isn't a 5.

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?

Usage is implied by the enumeration of content kinds and by the phrase 'to the target', which hints that presets need a target node. There is no explicit when-to-use / when-not-to-use statement and no reference to alternative tools for adjacent tasks. Adequate but leaves routing to inference.

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