Skip to main content
Glama

blender_vrm_metadata

Manage VRM avatar metadata including first-person offset, blink/viseme mappings, spring bone physics, and look-at settings. Export configuration for VRM-compatible platforms.

Instructions

Comprehensive VRM metadata management for avatar configuration.

Handles all VRM-specific settings required for proper avatar functionality in VRChat, VRoid Studio, and other VRM-compatible platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoVRM metadata operation typeset_first_person_offset
offset_xNoFirst person X offset from head bone
offset_yNoFirst person Y offset from head bone
offset_zNoFirst person Z offset from head bone (typically 0.1-0.2)
viseme_mappingsNoCustom viseme to shape key mappings
blink_shape_keyNoShape key name for blink animationblink
spring_bone_settingsNoSpring bone physics configuration
look_at_settingsNoEye tracking look-at configuration
output_pathNoPath for metadata export//vrm_metadata.json
include_spring_bonesNoInclude spring bone data in export
include_look_atNoInclude look-at data in export
target_armatureNoSpecific armature to modify
target_meshNoSpecific mesh for facial operations

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 carries full burden. It does not disclose behavioral traits like whether it reads/writes, modifies Blender objects, or only exports metadata. The generic phrase 'comprehensive management' lacks specificity.

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?

The description is two sentences, concise and to the point, with no superfluous words.

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 13 parameters and no annotations, the description is too brief. It does not explain the tool's overall workflow, return value, or how parameters interact, making it incomplete for an agent.

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%, so baseline is 3. The description does not add extra meaning to parameters beyond what the schema already provides.

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 clearly states it manages VRM metadata for avatar configuration, specifying platforms like VRChat and VRoid Studio. It distinguishes from siblings as no other tool handles VRM metadata.

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

Usage Guidelines3/5

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

The description implies usage for VRM settings but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives.

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