Skip to main content
Glama

set_material_nodes

Build or modify a material's shader node setup by applying structured node operations, supporting 3D shading workflows in Blender MCP.

Instructions

Apply structured node operations to a material.

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>",
      "operations": "<operations>"
    },
    "name": "set_material_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
operationsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and falls well short. "Apply" signals a mutation, but it doesn't say whether existing nodes are replaced or appended to, whether the operation is reversible, what permissions are needed, or what happens on invalid operations.

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

Conciseness3/5

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

One short sentence, front-loaded and free of padding, so nothing is wasted. But the brevity stems from under-specification rather than disciplined conciseness — it is short because it says almost nothing.

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 needn't be explained, but the tool is a mutating, parameter-opaque operation with no annotations. Given that complexity, the description should define the operations format and mutation semantics; it does neither.

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%, so both parameters are undocumented in structured data. The description doesn't compensate: it never clarifies that "name" identifies the target material, nor does it explain the shape of the "operations" array of opaque objects, which is the crux of calling this tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Apply structured node operations to a material" gives a verb (apply) and a resource (material node operations), which distinguishes it from siblings like set_material_color or set_material_properties. However, "structured node operations" is vague — it never says whether this builds a shader node graph, edits existing nodes, or what an operation is.

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 when-to-use guidance, no prerequisites, and no mention of the obvious sibling get_material_nodes for reading the current node setup. The agent must infer from the name alone that this is the write counterpart to the getter.

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