Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_shader_node_property

Configure node-level shader settings, such as Math operation or Voronoi feature type, by applying values to a chosen material, node, and property.

Instructions

Set a node-level property (not a socket) on a shader node.

These are the dropdowns and checkboxes on the node body rather than its input sockets: Math 'operation', Mix 'blend_type', Voronoi 'feature' (use 'DISTANCE_TO_EDGE' for vein and crack patterns), Wave 'wave_type' and 'bands_direction', Noise 'noise_dimensions'.

Args: material_name: Name of the material. node_name: Name of the node. property: Property name. Must be one of the allowed node properties. value: String enum identifier, number, or boolean.

Returns: Dict with the node, property, and the value that was applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
propertyYes
node_nameYes
material_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / property / enum
      Added value: +[
+  "attribute_name",
+  "attribute_type",
+  "axis",
+  "bands_direction",
+  "blend_type",
+  "clamp",
+  "clamp_factor",
+  "clamp_result",
+  "component",
+  "convert_from",
+  "convert_to",
+  "data_type",
+  "distance",
+  "distribution",
+  "extension",
+  "factor_mode",
+  "feature",
+  "from_instancer",
+  "gradient_type",
+  "interpolation",
+  "interpolation_type",
+  "invert",
+  "mode",
+  "noise_dimensions",
+  "noise_type",
+  "normalize",
+  "offset",
+  "offset_frequency",
+  "operation",
+  "projection",
+  "rings_direction",
+  "rotation_type",
+  "space",
+  "squash",
+  "squash_frequency",
+  "subsurface_method",
+  "turbulence_depth",
+  "use_clamp",
+  "uv_map",
+  "vector_type",
+  "voronoi_dimensions",
+  "wave_profile",
+  "wave_type"
+]
  2. Addedv1.3.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the nature of the operation (node-body properties rather than sockets) plus a domain hint ('DISTANCE_TO_EDGE' for vein/crack patterns). It still omits side-effect, permission, or reversibility information, leaving meaningful behavioral gaps.

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?

Front-loaded purpose sentence followed by a scoping clarification and a compact example list, then Args/Returns. Every section earns its place; the property-example list is slightly long but informative rather than wasteful.

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

Completeness4/5

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

An output schema exists and the description even summarizes the return dict, so return values are covered. For a four-param mutation tool the description supplies enough to invoke it correctly, though the absence of any safety or side-effect note is a minor 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 description must compensate, and it does: it names all four parameters, clarifies that property 'must be one of the allowed node properties', and explains value as 'string enum identifier, number, or boolean'. This adds real meaning beyond the bare schema, though it doesn't document individual enum members.

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?

States a specific verb+resource (set a node-level property on a shader node) and immediately sharpens the scope with 'not a socket', which cleanly separates it from the socket-oriented sibling set_shader_node_input. The examples of concrete properties (Math 'operation', Mix 'blend_type', Voronoi 'feature') make the intent unmistakable.

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 'not a socket' clause implicitly routes the agent toward this tool for dropdowns/checkboxes and away from set_shader_node_input, giving clear context. However, it never names the alternative tool explicitly, so the routing is inferential rather than spelled out.

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