Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_material_property

Idempotent

Set a Principled BSDF property in Blender, such as base color, metallic, roughness, or emission, by specifying the material name, property, and value.

Instructions

Set a Principled BSDF property. Properties: base_color, metallic, roughness, specular, transmission, emission_color, emission_strength, alpha, normal_strength.

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": {
      "material": "<material>",
      "property": "<property>",
      "value": "<value>"
    },
    "name": "set_material_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
materialYes
propertyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The idempotentHint already covers repeat-safety. The description adds the list of valid property names but does not disclose failure modes, value constraints, or whether only Principled BSDF materials are supported. That is a modest addition beyond the annotation.

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, one action and one list; every token is functional and the key information is front-loaded.

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 tool is simple and an output schema exists, but the description omits value format details for color/vector properties and how the material is addressed. It is adequate for basic scalar properties but less safe for complex ones.

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 0%, so the description carries the burden. It supplies the only enumeration of valid `property` values, but leaves `material` and `value` semantics vague—no per-property value shape or material identifier conventions. This is partial but not full compensation.

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 identifies the operation (set) and the resource (Principled BSDF property), listing valid property names. This distinguishes it from sibling setter tools like set_light_property or set_world_property.

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

Usage Guidelines4/5

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

The phrase 'Set a Principled BSDF property' establishes the tool is for modifying material shader properties, and the property list clarifies intended scope. It does not explicitly contrast with siblings or state when not to use it, but the context is unmistakable.

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