Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

content_search

Read-onlyIdempotent

Locate installed Daz Studio content—figures, clothing, hair, poses, materials, props, lights—by query, kind, folder, or generation; get absolute paths for loading and thumbnails for previews.

Instructions

Searches the installed content: figures, characters, clothing, hair, poses, materials, props, lights. Returns absolute paths to pass to content_load, and thumbnails for content_thumbnail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "content_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNofigure, character, clothing, hair, pose, material, shape, prop, light, scene, scene_subset...
limitNo
queryNoWords that must all appear in the file path, e.g. 'jeans' or 'genesis 9 walk'. Empty lists everything that matches the filters.
folderNoOnly inside this library folder, e.g. 'People/Genesis 9/Poses'.
offsetNo
generationNoOnly content made for this figure generation, e.g. 'Genesis 9' (figure_info reports it).
refresh_indexNoRebuild the index (after installing content).

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 already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new information beyond them: what the return payload contains (absolute paths plus thumbnails) — valuable since there is no output schema. It omits that refresh_index triggers a costly index rebuild, though the schema does note that.

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?

Two sentences, zero filler, with the resource scope front-loaded and the return/chaining contract second. Every clause carries information an agent needs.

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 7-parameter, no-output-schema search tool, the description covers purpose, scope, and return shape well. Minor gaps remain around pagination (limit/offset) and the behavioral cost of a full index rebuild, both of which are only discoverable in the 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 71%, so most parameters (query, folder, generation, refresh_index) are already documented inline. The description only restates the set of content kinds already present in the kind enum, adding no new semantics about filtering, pagination, or how query terms are matched.

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 ("Searches") and an enumerated resource set (figures, characters, clothing, hair, poses, materials, props, lights) over installed content. It also names the downstream consumers (content_load, content_thumbnail), which separates it from those siblings without needing to open any schema.

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?

The workflow positioning is clear: results are absolute paths meant to be passed to content_load, with thumbnails for content_thumbnail, so an agent knows this is the discovery step preceding a load. It stops short of explicit exclusions or naming folder-level browsing (content_libraries) as an alternative.

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