Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wizard_material_preset

Apply a complete PBR material preset to an object in a single call. Choose from ready-made presets like metal, wood, glass, or skin to set correct roughness, metallic, and subsurface values.

Instructions

Apply a complete PBR material preset to an object in one call.

Pre-configured recipes for common materials with correct roughness, metallic, and subsurface values.

Args: object_name: Target object. preset: metal, chrome, gold, wood, glass, plastic, concrete, fabric, leather, rubber, ceramic, marble, skin, emissive. color: Override base color [R, G, B]. None = preset default.

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": {
      "object_name": "<object_name>"
    },
    "name": "wizard_material_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
presetNometal
object_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the main behavior and material-channel coverage, but it does not explain side effects such as whether existing materials are replaced, whether a new material slot is created, or whether the operation is reversible.

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 compact and front-loaded with the main purpose, followed by a clean Args list. Every sentence adds value and there is no redundant restating of the schema.

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

Completeness3/5

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

All parameters are documented and the operation's core purpose is clear, but an agent still lacks guidance on important mutation details: what happens to existing materials, which material slot receives the preset, and what the tool returns. For a no-annotation, no-output-schema mutation tool, this is a noticeable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the inline Args section must compensate. It does: object_name is defined as the target, preset values are enumerated, and color is described as an override with a None default. The color range or value scale is not specified, but this is still a strong compensation.

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 states a specific action ('Apply a complete PBR material preset to an object in one call') and a clear resource. It implicitly differentiates from siblings by emphasizing complete presets, but it never names alternatives like batch_material_preset or configure_glass_material.

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 phrasing 'in one call' and 'Pre-configured recipes for common materials with correct roughness, metallic, and subsurface values' implies the tool is for quick, realistic material assignment. However, it does not explicitly state when to choose this over assign_material, set_material_property, or the configure_*_material tools.

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