Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

package_install

Installs content packages from other stores into a Daz Studio content library, registers the library, returns paths for loading/importing new items and meshes, and records files for later removal.

Instructions

Installs a content package from another store (Renderosity, RuntimeDNA, CGBytes, free sites): finds its content root, copies it into a content library, makes sure Daz Studio has that library, and returns the new items (paths for content_load) and any loose meshes (paths for import_mesh). Records every file so package_uninstall can remove them.

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": "package_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName to record the package under (default: the file name).
pathYesAbsolute path of the .zip (or unpacked folder).
libraryNoContent library folder to install into; default the third-party library (~/Documents/DAZ 3D/Third Party Library), which is added to Daz if needed.
overwriteNoReplace files that another package installed with different contents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so safety is partly covered, but the description still adds real value: it copies files into a library, mutates Daz Studio's library configuration ("makes sure Daz Studio has that library"), and keeps a file manifest enabling removal. Reversibility is disclosed via the package_uninstall link. It does not warn that the default install path is outside the open-world hint's scope or discuss failure/partial-install behavior.

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 dense sentence sequence with the primary action front-loaded, followed by the workflow and then the return contract. Every clause carries information, though the nested parentheses and colon-chaining make it slightly harder to scan than a bulleted step list would be.

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?

There is no output schema, and the description compensates by describing the return payload (new item paths for content_load, loose meshes for import_mesh), which is exactly what an agent needs to chain calls. Combined with the undo path and default library behavior, it is nearly complete; only error/partial-failure semantics are 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 description coverage is 100%, so all four parameters (name, path, library, overwrite) are already documented in the schema, including the default third-party library. The description adds no parameter-level detail beyond the schema — its mention of content roots and loose meshes is about behavior, not arguments. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ("Installs a content package from another store") and enumerates the actual sources it handles (Renderosity, RuntimeDNA, CGBytes, free sites). It also lays out the concrete sub-steps — find content root, copy into library, register library with Daz Studio — which makes it unmistakable against siblings like package_uninstall or package_inspect.

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?

The description establishes the context clearly (installing third-party content) and routes the agent downstream, naming content_load for returned item paths and import_mesh for loose meshes, plus package_uninstall for reversal. It stops short of explicit exclusions such as when to prefer package_inspect first or when not to install, so it is context-rich but not a full when/when-not rule set.

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