Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_material

Creates a verified Principled BSDF material in the active Blender session with configurable PBR properties (base color, roughness, metallic, IOR, alpha, specular).

Instructions

Create a verified Principled BSDF material in the active Blender session with configurable PBR properties (base color, roughness, metallic, ior, alpha, specular).

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

Input Schema

NameRequiredDescriptionDefault
iorNoIndex of Refraction for dielectric transmission/Fresnel (default 1.45).
nameYesUnique name for the new material.
alphaNoTransparency/alpha value (0.0 = invisible, 1.0 = opaque).
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
metallicNoMetallic reflectivity (0.0 = dielectric, 1.0 = full metallic).
specularNoSpecular reflectance level (0.0 to 1.0).
roughnessNoSurface roughness (0.0 = mirror smooth, 1.0 = completely diffuse).
base_colorNoBase color RGBA or RGB list [r, g, b, (a)] with values between 0.0 and 1.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and falls short for a scene mutation. It does not say what happens on a name collision (the schema declares the name must be unique), whether the material is auto-assigned to anything, what is returned, or whether the operation is undoable; 'verified' is unexplained.

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?

One front-loaded sentence with no filler and no hedging. The trailing property list mildly duplicates schema content but is short and helps scanning.

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

Completeness3/5

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

For a 9-parameter mutation with no annotations and no output schema, the description omits the return value (material name/handle) and the name-collision behavior, which the agent needs in order to chain into assign_material. It is adequate to identify the tool but not to call it confidently end-to-end.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents ranges, defaults, and meanings for all nine parameters. The description only names the property groups (base color, roughness, metallic, ior, alpha, specular) and adds nothing about name/task_id/approved beyond what structured fields provide; baseline 3 applies.

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?

States a specific verb and resource ('Create a verified Principled BSDF material') plus the scope ('in the active Blender session') and the configurable surface, so an agent knows exactly what is produced. It does not explicitly distinguish itself from siblings such as configure_material_shader or assign_material, which an agent must infer from the word 'Create'.

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 when-to-use guidance: nothing says to prefer this over configure_material_shader for an existing material, or that assign_material is a separate step. The only contextual hint is 'active Blender session', which describes environment rather than selection criteria.

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