Skip to main content
Glama
yi00it

blender-asset-mcp

by yi00it
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_material

Create a Blender Principled BSDF material with defined base color, metallic, roughness, transparency, and emission settings. Assign it to objects or reuse an existing material by name.

Instructions

Create a Principled BSDF material.

Colors are [r, g, b] or [r, g, b, a] floats in 0..1 LINEAR space -- not 0-255 and not sRGB hex. Returns the material's resulting properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iorNoIndex of refraction; 1.45 glass, 1.5 plastic
nameYesMaterial name
alphaNoBelow 1 also needs blend_method='BLENDED'
metallicNo0 for non-metals, 1 for bare metal. Values in between are physically wrong for game PBR.
assign_toNoObjects to assign the new material to immediately
roughnessNo
base_colorNo[r, g, b] or [r, g, b, a], each 0..1 (linear)
blend_methodNoTransparency handling in EEVEE
emission_colorNo[r, g, b] or [r, g, b, a], each 0..1 (linear)
reuse_existingNoReuse a material of this name instead of failing
emission_strengthNo
use_backface_cullingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It usefully warns about linear color space and states that the material's properties are returned, which adds value. However, it does not mention what happens when a material name already exists, whether it overwrites, or what side effects occur beyond creation.

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 short sentences deliver the main purpose first, then the critical usage caveat about color encoding. There is no filler or redundant restatement 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?

The description covers the most error-prone detail (color space) and the return value, but for a 12-parameter material creation tool with no annotations, it omits duplicate-name behavior and the optional assignment behavior. Much of the parameter context is already in the schema, so the description is adequate but not complete.

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?

The description adds meaningful color-format semantics beyond the schema by explicitly defining linear [r,g,b]/[r,g,b,a] floats and warning against 0-255 or sRGB hex. Schema coverage is already 75%, so the color-format clarification is a valuable supplement rather than a compensation for missing schema.

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 opens with a specific verb and resource: 'Create a Principled BSDF material.' This clearly separates it from material inspection and assignment siblings like list_materials, get_material, and assign_material, which have different actions.

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?

No guidance is given for when to use create_material versus alternatives; there is no mention of when to prefer set_material_properties or assign_material instead. The intended context is implied by the name and the creation verb, but exclusions and alternatives are not stated.

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