Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

package_inspect

Read-onlyIdempotent

Inspects a content package before installation, showing its Daz content root, loadable files, loose meshes, extras and problems. Writes nothing.

Instructions

Looks inside a content package before installing it: where its Daz content root is (data, People, Props, Runtime...), which files can be loaded, loose OBJ/FBX meshes, extras and problems. Nothing is written.

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": {
      "path": "<path>"
    },
    "name": "package_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of a .zip from another store, or of a folder already unpacked.

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; 'Nothing is written' reinforces but does not add to that. The real added value is the enumeration of what the inspection surfaces (content root, loadable files, loose meshes, extras, problems), which tells the agent what behavior to expect from a read-only scan.

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, front-loaded with the core action and immediately followed by the concrete outputs and the no-write guarantee. No filler or redundant 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?

With no output schema, the description carries the return-value burden and does so by listing the categories of findings. It leaves 'problems' and 'extras' vaguely defined, which is a minor gap for an inspection tool an agent must interpret results from.

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?

Only one parameter, and the schema already fully documents it at 100% coverage (absolute path of a .zip or a folder already unpacked). The description adds no further syntax, validation or path-format detail beyond what the schema states, so 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?

States a specific verb and resource (inspect inside a content package) and names the concrete things it reports: Daz content root, loadable files, loose OBJ/FBX meshes, extras, problems. The phrase 'before installing it' also separates it from package_install without needing the sibling's 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?

'before installing it' gives a clear usage context and implies the natural alternative (package_install) is a separate, later step. It stops short of stating explicit when-not conditions or naming alternatives outright, so it is clear context rather than full routing guidance.

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