Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

place_on

Positions a posed figure on a prop such as a seat, bed, or step by aligning hips, back, or feet, then reports a fit check.

Instructions

Puts a posed figure on a prop: hips on a seat (turned to face out, against the backrest, knees clear of the seat front), back on a bed, feet on a step. Then reports fit_check.

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": {
      "figure": "<figure>",
      "prop": "<prop>"
    },
    "name": "place_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo[x, z] world point for the contact.
propYesProp to put it on.
sinkNocm the contact sinks into a soft cushion or mattress.
facingNoYaw in degrees; auto faces out of a seat.auto
figureYesFigure label, already posed (sitting, lying...).
contactNoWhat rests on the surface: seat = hips (sitting), back = lying face up, front = face down, feet = standing.seat
surfaceNoIndex from prop_surfaces; default picks one for the contact.
back_gapNoSeat: cm between backrest and back (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a non-destructive write in a closed world, and the description adds behavior beyond that: the figure is snapped to a contact point, auto-facing turns it out of a seat, cushion sink is applied, and a fit_check is reported as a side effect. It does not say what happens if the prop is occupied or the figure is unposed, which would have been the last piece.

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 that leads with the action and then enumerates contact cases, with no filler. The nested parentheses load a lot of qualifiers into one clause, which makes it denser than it needs to be, but nothing is wasted.

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 8 parameters, full schema coverage, and no output schema, the description carries the return-value burden and does so by mentioning the fit_check report. Orientation and contact behavior are covered. Remaining gaps are failure modes and preconditions on the figure's pose, which the schema partially covers.

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 every parameter already carries its own explanation and the baseline is 3. The prose reinforces the contact choice (hips/back/feet, turned to face out, knees clear of the seat front) and implies the back_gap default, but names no parameter and adds no syntax or format detail the schema lacks.

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 gives a specific verb and resource ('Puts a posed figure on a prop') and concretizes it with three contact cases: hips on a seat, back on a bed, feet on a step. It also notes the tool ends by reporting fit_check, which tells an agent what it gets back. It does not explicitly distinguish itself from placement-adjacent siblings such as anim_foot_contact, so it stops short of 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 only implied: the figure must be posed first (the schema hints at 'already posed (sitting, lying...)'), and the tool is for static placement against a prop surface. There is no explicit when-not guidance, no statement about alternatives, and no instruction on whether a separate fit_check call is still needed after this one.

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