Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_color_ramp_interpolation

Set a ColorRamp node's interpolation and color mode to control blending between stops, creating hard-edged bands, softer falloff, or hue sweeps in Blender materials.

Instructions

Set how a ColorRamp blends between its stops.

'CONSTANT' gives hard-edged bands with no blending, which is what turns a noise or voronoi texture into discrete regions: scale plates, cracked mud, stylised cel shading. 'EASE' and 'B_SPLINE' give softer falloff than 'LINEAR'. Set color_mode to 'HSV' to sweep through hues between two stops rather than blending through grey.

Args: material_name: Name of the material. node_name: Name of the ColorRamp node. interpolation: One of EASE, CARDINAL, LINEAR, B_SPLINE, CONSTANT. color_mode: Optional. One of RGB, HSV, HSL. Omit to leave unchanged.

Returns: Dict with the applied interpolation and color mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_nameYes
color_modeNo
interpolationYes
material_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / color_mode / enum
      Added value: +[
+  "HSL",
+  "HSV",
+  "RGB"
+]
    • addedInput schema / properties / interpolation / enum
      Added value: +[
+  "B_SPLINE",
+  "CARDINAL",
+  "CONSTANT",
+  "EASE",
+  "LINEAR"
+]
  2. Addedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the effect of each interpolation mode and that omitting color_mode leaves it unchanged. It also states the return shape. It does not cover prerequisites (e.g., node must already exist) or error behavior, so it stops short of full disclosure.

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 useful detail, Args, and Returns. Slight redundancy in re-listing the enum values already in the schema, but overall tight with no filler.

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?

With an output schema present, the description needn't explain return values in depth, and it briefly does anyway. For a four-parameter shader-node mutation with no annotations, it covers parameter meaning and mode effects adequately; only prerequisite/error context is missing.

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 documents all four parameters with valid values and the key semantic detail that omitting color_mode leaves it unchanged. The enum listings largely mirror the schema enums, adding limited value there, but the mode-effect explanations add real meaning.

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 and resource ('Set how a ColorRamp blends between its stops'), scoping to a material's named ColorRamp node. An agent can distinguish it from siblings like set_color_ramp_element, add_color_ramp_element, and get_color_ramp from the description alone.

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?

Gives concrete when-to-use guidance for the parameter values: CONSTANT for hard-edged bands (noise/voronoi, cel shading), EASE/B_SPLINE for softer falloff than LINEAR, HSV to sweep hues instead of blending through grey. It does not, however, route the agent against sibling tools such as set_color_ramp_element.

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