Skip to main content
Glama

create_basic_shader

Creates a basic Principled material with optional name and color, letting you assign simple surface shading to 3D objects in Blender.

Instructions

Create a basic Principled material.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_basic_shader"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, "Create" only implies a mutating operation and "Principled" identifies the shader model. The description does not clarify whether it creates a material datablock, builds or replaces a node tree, assigns the material to an object, or handles defaults and repeated names.

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 single sentence is direct, front-loaded, and free of filler. Its brevity is clean but under-informative for a tool whose schema and annotations provide little additional documentation.

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?

The output schema reduces the need to document return values, and the operation itself is relatively simple. Nevertheless, the absence of annotations and parameter descriptions leaves important invocation behavior and sibling-selection questions unresolved.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention either name or color. In particular, color's component order, expected array length, value range, and null/default behavior remain unexplained, so the description does not compensate for the sparse schema.

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 provides a specific verb and resource: creating a material using the Principled shader. It does not, however, distinguish this simplified tool from create_material or the specialized material-creation siblings.

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?

The word "basic" loosely suggests use for a simple default material, but there is no explicit guidance on when to choose this over create_material, create_metallic_material, or other material tools. No prerequisites, exclusions, or when-not-to-use conditions are given.

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