Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_mesh

Imports loose OBJ or FBX models into Daz Studio at the correct scale without the importer dialog, returning the new node, its size, and surfaces for clothing workflows.

Instructions

Imports a loose OBJ or FBX model (Sketchfab, CGTrader, Blender, a package's meshes) into the scene with the right size, without the importer dialog. Returns the new node, its size in cm and its surfaces. Clothing modeled for a figure then goes through wearable_from_mesh.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of an .obj or .fbx file.
takeNoFBX: animation take to import.
labelNoLabel for the imported node.
unitsNoUnits the file is in. auto: OBJ is guessed from its size, FBX uses the units stored in the file.auto
heightNoScale it uniformly to this height in cm (e.g. 180 for a person).
optionsNoExtra importer settings (advanced).
up_axisNoOBJ only: Z for Z-up files that import lying down.Y
positionNo[x, y, z] cm.
drop_to_floorNoPut its lowest point on the floor. Leave off for clothing modeled around a figure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations flag this as a non-read-only, non-destructive, non-open-world operation; the description adds real value on top by declaring that no interactive dialog appears and by naming the return payload rather than leaving the result shape unknown. It does not cover side effects like name collisions, re-importing over an existing node, or failure modes for malformed files.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool does, followed by the return contract and the sibling hand-off. No filler, no restating of the name or title, and the follow-up tool mention is placed where an agent would act on it.

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?

With nine parameters, no output schema, and an all-documented schema, the description supplies what the structured fields cannot: the return values, the dialog-free behavior, and the sizing intent. What is missing is edge-case behavior, such as overwrite semantics or what happens when units/height conflict, which matters for a mutating import.

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% and the enum-backed units and up_axis parameters are fully explained there, so the schema already carries the parameter burden. The description only gestures at sizing behavior ('with the right size'), which hints that units/height interact, but adds no format or precedence detail beyond the schema. Baseline 3 is appropriate.

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 (imports) plus the accepted resource formats (loose OBJ or FBX), the scope ('into the scene'), the outcome ('with the right size, without the importer dialog'), and the return payload (new node, size in cm, surfaces). It also implicitly separates itself from library/content loading and animation import by restricting to 'loose' mesh files.

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?

Gives a clear routing rule for the most likely ambiguity: clothing modeled for a figure should go through wearable_from_mesh after this import. It also frames when this beats the manual path ('without the importer dialog'). It stops short of explicit exclusions, such as pointing animation files at anim_import or packaged content at content_load.

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