Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

material_list

Read-onlyIdempotent

Lists a node’s surfaces with their shader and main material values, including color, roughness, and maps, to inspect or filter material properties.

Instructions

Lists the surfaces of a node with their shader and main values (color, roughness, maps...).

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

Input Schema

NameRequiredDescriptionDefault
nodeYesLabel of a figure, clothing, hair or prop.
queryNoOnly properties whose label contains this.
surfacesNoOnly these surfaces.
all_propertiesNoEvery property, not only the main ones (long).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing what is returned (surfaces with shader and main values), which matters because no output schema exists; it does not discuss the cost of all_properties or result size.

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?

One front-loaded sentence with the resource and the returned fields; the parenthetical is compact illustration rather than filler. Nothing is redundant or buried.

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 read-only, four-parameter list tool with full schema coverage and complete annotations, the description supplies what structured data cannot: the shape of the returned values. It could still mention filtering behavior for query/surfaces, but nothing an agent needs to invoke it correctly is missing.

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 is already documented in the input schema, establishing a baseline of 3. The phrase "main values" mirrors the all_properties default but adds no syntax or format detail 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?

The description uses a specific verb and resource ("Lists the surfaces of a node") and names the returned content (shader, color, roughness, maps), which lets an agent distinguish it from material_set without opening the schema. It does not explicitly name that sibling, 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: an agent can infer this is the read/inspect counterpart to material_set, but the description never states when to call it, when not to, or which alternative handles mutation. No exclusions or prerequisites are given.

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