Skip to main content
Glama

set_material_properties

Set common Principled BSDF properties on a named material to control its surface appearance in Blender.

Instructions

Set common Principled BSDF properties.

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": {
      "name": "<name>",
      "properties": "<properties>"
    },
    "name": "set_material_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
propertiesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It indicates a mutation by saying "Set," but does not explain whether values are merged or replaced, whether existing properties are preserved, what happens on invalid property names, or what permissions or state are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. Its concision is appropriate structurally, though the word "common" adds ambiguity rather than useful specificity.

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?

An output schema exists, so return values do not need description coverage. However, for a two-parameter mutation tool with a nested free-form properties object and 0% parameter description coverage, the description is too thin to fully prepare an agent to invoke it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only hints that the properties object contains Principled BSDF properties. It does not clarify that "name" likely identifies the material, what keys are valid in the nested properties object, or what value types are expected.

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 uses a specific verb, "Set," and a recognizable resource, "Principled BSDF properties," so the basic operation is clear. It does not explicitly distinguish itself from siblings such as set_material_color or set_material_nodes, and "common" is vague about which properties are supported.

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?

There is no guidance on when to use this tool versus set_material_color, set_material_nodes, or other material tools. It also omits prerequisites, such as whether the material must already exist, and gives no exclusions or context about when this tool is inappropriate.

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