Skip to main content
Glama
Sign In
Daz3D-MCP

Daz3D-MCP

by MictlanLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anim_file_inspect

Read-onlyIdempotent

Inspect BVH or FBX animation files without importing them to read frame data, frame rate, length, bones, rig type, and optional bone mappings for a figure.

Instructions

Reads a BVH or FBX animation without importing it: frames, frame rate, length, bones, which rig it is (Mixamo, CMU mocap, Unreal, 3ds Max Biped, Genesis) and, with figure, which bones map.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of a .bvh or .fbx animation (Mixamo, mocap...).
takeNoFBX: animation take.
figureNoFigure to check the bone map against.

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, and non-destructive, and the description reinforces this with the meaningful consequence that the file is not imported into the scene. It also discloses the returned facts, which is the key behavioral context for a read tool. It does not cover failure behavior for malformed or unsupported files, which keeps it below a 5.

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?

It is a single, front-loaded sentence with no filler; the verb and no-import constraint come first and the enumerated outputs follow. 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?

With no output schema, the description usefully enumerates what the call reports, and the 3-parameter schema is fully documented. The only gap is that it never mentions how the optional take parameter affects results for FBX files, minor for a read-only inspection 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 description coverage is 100%, so all three parameters (path, take, figure) are already documented with defaults. The description only echoes figure's purpose ('with figure, which bones map') and says nothing beyond the schema about take or the accepted path formats, 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 gives a specific verb (reads) and resource (BVH or FBX animation) and immediately scopes it against the obvious sibling behavior by saying 'without importing it.' It also enumerates exactly what introspection it returns (frames, frame rate, length, bones, rig family, and the bone map when figure is supplied), so an agent can distinguish it from anim_import at a glance.

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 phrase 'without importing it' establishes the pre-import inspection context clearly, and 'with figure, which bones map' signals the conditional case for opting into bone-mapping. It stops short of naming anim_import as the alternative for an actual import or stating when inspection is unnecessary, so it is clear but not fully prescriptive.

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