Skip to main content
Glama

blender_validation

Validate 3D models and avatars against platform-specific requirements for VRChat, Unity, and Resonite. Checks geometry, materials, rigging, and transforms to identify issues before upload.

Instructions

Comprehensive validation tools for avatars and 3D models.

Performs pre-flight checks to ensure models meet platform requirements for VRChat, Resonite, Unity, and other 3D platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoValidation operation typevalidate_avatar
target_platformNoTarget platform ("vrchat", "resonite", "unity", "generic")vrchat
check_materialsNoWhether to validate materials and draw calls
check_riggingNoWhether to validate bone structure and rigging
check_transformsNoWhether to check for unapplied transforms
check_texturesNoWhether to validate texture requirements
polycount_limitNoCustom polycount limit override
material_limitNoCustom material count limit override
bone_limitNoCustom bone count limit override
object_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It states the tool performs checks but does not describe whether it modifies the model, returns errors, or requires any permissions. The read-only nature and side effects are not clarified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with only two sentences, front-loading the core purpose. However, it could be slightly more informative without sacrificing brevity, such as mentioning that it reports issues or lists validation results.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters and an output schema (not shown), the description fails to mention what the tool returns (e.g., a list of validation errors, pass/fail). For a validation tool, this is a notable gap. The description is too brief for the tool's complexity.

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 high (90%), so the schema already details most parameters. The description adds little beyond naming the tool as 'comprehensive validation tools' and mentioning platforms. It does not explain the meaning of various operation types or parameter interplay beyond what the schema provides.

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 clearly states that the tool performs comprehensive validation and pre-flight checks for avatars and 3D models across multiple platforms (VRChat, Resonite, Unity). It uses specific verbs and resources, though it does not explicitly distinguish itself from sibling tools that may also perform validation aspects (e.g., blender_mesh, blender_rigging).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or comparative advice. For a tool with many sibling tools covering similar domains, this omission is significant.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server