Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

figure_info

Read-onlyIdempotent

Inspect a Daz figure's generation, height, clothing, active shape dials, posed bones, and surfaces, plus optional joint limits and body-part locations.

Instructions

Describes a figure: generation, height, what it wears, the shape dials in use, the posed bones and its surfaces; optionally joint limits and where its body parts are.

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>"
    },
    "name": "figure_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
figureYesFigure label.
limitsNoBones whose joint limits to report, e.g. ["l_upperarm", "l_thigh"]: [min, max] degrees per axis.
all_bonesNoList every bone name (for pose_bones).
landmarksNoLowest world point of each body part (hips, thighs, feet, hands...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds what categories of data are reported, which is useful, but says nothing about failure modes for an unknown figure label or the cost of listing every bone with all_bones.

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?

A single front-loaded sentence that packs the enumerated facets and flags the two optional outputs; no filler, no repetition of the title, and the required resource is named first.

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 no output schema, the description carries the burden of explaining return content and does so by listing the reported facets plus the two opt-in extras. Reasonably complete for a four-parameter read tool, with only error/precondition behavior left unstated.

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 schema already documents figure, limits, all_bones and landmarks with defaults and format examples. The description only loosely echoes the limits and landmarks options and never mentions all_bones, so it adds little meaning beyond the schema.

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 ("Describes a figure") and enumerates the exact facets returned: generation, height, clothing, shape dials, posed bones, surfaces. An agent can tell it is a per-figure introspection tool, though it never explicitly distinguishes itself from siblings like scene_info.

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 phrase "optionally joint limits and where its body parts are" hints at when to set the limits/landmarks flags, but there is no statement of when to prefer this over scene_info or fit_check, and no prerequisites such as loading a figure first.

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