Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mesh_inspect

Read-onlyIdempotent

Inspect OBJ or FBX files without importing to get dimensions, likely units, surfaces, textures and any rigging or animation before you load the asset.

Instructions

Reads an OBJ or FBX without importing it: size in file units, the units it most likely uses, surfaces, textures found and missing, whether it is rigged or animated.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of an .obj or .fbx file.

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 and closed-world, so safety is covered. The description adds the genuinely useful behavioral fact that the file is not imported, meaning no scene mutation, and it discloses what information is surfaced. It does not cover failure behavior for invalid/short paths or cost on very large files.

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 sentence, front-loaded with the verb and the key constraint, then a colon-delimited list of what is reported. 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 burden of saying what comes back, and it does so by enumerating the reported facts. It leaves the return shape (field names, how 'likely units' is expressed, how missing textures are listed) unspecified, which is a modest remaining gap for a read-only tool.

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 coverage is 100% and the single parameter is already documented as an absolute path to a .obj or .fbx file. The description's mention of OBJ/FBX restates the schema rather than adding format, encoding, or path-resolution detail, 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?

States a specific verb (reads/inspects) against a specific resource (OBJ or FBX file) and enumerates the concrete outputs: size in file units, likely units, surfaces, textures found/missing, rig/animation presence. The phrase 'without importing it' immediately separates it from an ingest-style sibling like import_mesh.

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 'without importing it' framing gives a clear selection rule: use this for a dry look at a file when you do not want it in the scene. It stops short of naming an explicit alternative or stating when-not to use it, 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