Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

prop_surfaces

Read-onlyIdempotent

Measures a prop's flat surfaces where a figure can sit, lie, or stand, returning height, size, center, and facing direction for seats with backrests.

Instructions

Measures the flat surfaces of a prop where a figure can sit, lie or stand: height, size, center and, for a seat with a backrest, which way it faces (facing_yaw).

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": {
      "node": "<node>"
    },
    "name": "prop_surfaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesProp label: chair, sofa, bed, table, stairs...
max_tiltNoDegrees a surface may slope.
min_areaNoSmallest surface, cm2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world query. The description adds value beyond those annotations by disclosing what is returned (height, size, center) and clarifying the semantics of facing_yaw as the orientation of a seat with a backrest, which is not something annotations can convey.

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 tightly packed sentence that front-loads the verb and purpose and then lists the returned measures. Every clause carries information and there is no filler or restatement of the tool name.

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?

For a three-parameter read-only measurement tool with rich annotations, the description covers purpose, use intent and returned fields adequately. It stops short of describing output shape details such as whether multiple surfaces are returned per prop or how surfaces are ordered, which matters somewhat since there is no output schema.

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%, with node, max_tilt and min_area each documented including units and default values. The description only hints at one parameter domain via the example prop types in the schema ('chair, sofa, bed...') and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ('Measures the flat surfaces of a prop') and enumerates the exact outputs: height, size, center and facing_yaw. It also states the practical intent ('where a figure can sit, lie or stand'), so an agent can distinguish it from inspection tools like fit_check or figure_info without opening a schema.

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?

The use case is implied by the phrase 'where a figure can sit, lie or stand', which suggests calling it before seating or placing a figure on a prop. However, there is no explicit when-to-use/when-not guidance, no prerequisites, and no named alternative tool; the agent must infer the workflow context.

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