Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

content_add_library

Adds a folder to Daz Studio's content libraries so its assets become searchable, loadable, and able to find their data files, persisting across restarts. Choose Daz or Poser format.

Instructions

Adds a folder to Daz Studio's content libraries (it stays after a restart), so its content can be searched and loaded and finds its data files.

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_add_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoposer for a folder with a Runtime folder (Poser format content).daz
pathYesAbsolute path of a folder that holds Daz content (data, People, Props... inside).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish this is a non-read-only, non-destructive, non-open-world mutation, so the bar is lower; the description still adds real value by disclosing persistence ('it stays after a restart') and the successful outcome (content becomes searchable and loadable). It stops short of saying what happens on a duplicate or invalid path, which is the main remaining behavioral gap.

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 sentence, front-loaded with the action and resource, with the persistence and outcome details in a trailing clause. Slightly run-on ('searched and loaded and finds its data files') but nothing is wasted.

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

Completeness3/5

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

For a two-parameter mutation with no output schema, the description covers purpose, persistence, and the effect on searchability. It is still thin on edge behavior an agent would want before invoking a write, such as duplicate registration or an invalid path, so it is adequate but not complete.

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 100%, so both parameters are already documented, including the kind enum (daz/poser) and the meaning of path. The description restates that the folder holds Daz content but adds no new detail about the kind parameter or expected folder layout 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 and resource: adding a folder to Daz Studio's content libraries, with the downstream effect that its content becomes searchable/loadable. It clearly reads as the mutating counterpart to the read-only sibling content_libraries, though it never names that sibling explicitly.

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 effect clause ('so its content can be searched and loaded'), which tells an agent why to register a library, but there is no explicit when-not guidance, no mention of content_libraries/content_search as alternatives, and no prerequisites stated.

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