Skip to main content
Glama

blender_vrm_metadata

Manage VRM avatar metadata: set first-person offset, blink viseme mappings, spring bones, look-at, and export configuration.

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, and the description does not disclose behavioral traits such as whether changes are destructive, reversible, or require specific Blender versions/addons. It only mentions platform compatibility vaguely.

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 with no unnecessary words. Front-loaded with the purpose and context. Conciseness is excellent.

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?

Despite having an output schema (unknown content), the description is too high-level for a tool with 13 parameters and multiple sub-operations. It does not explain which operation to use for different tasks or provide workflow guidance, leaving significant gaps for an AI 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 the schema itself documents all parameters. The tool description adds no additional meaning beyond that baseline. A score of 3 is appropriate as the description does not detract but neither does it enhance.

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 VRM metadata management for avatar configuration, but does not explicitly list the specific operations (e.g., set first person offset, configure spring bones) that are evident from the input schema. This ambiguity may require the agent to inspect the schema for full purpose clarity.

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 provides no guidance on when to use this tool versus siblings (none are VRM-specific, but many Blender tools exist). It also does not state prerequisites, such as needing a VRM avatar loaded or platforms like VRChat.

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