Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

assign_material

Assign an existing material to an object in the active Blender scene, optionally targeting a specific material slot index or face indices. Use it to apply materials to objects without creating new ones.

Instructions

Assign an existing material to an object in the active scene, optionally targeting a specific material slot index.

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": {
      "target_name": "<target_name>",
      "material_name": "<material_name>"
    },
    "name": "assign_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
slot_indexNoOptional material slot index to assign into. If omitted or beyond existing slots, a new slot is appended.
target_nameYesTarget object name to assign the material to.
face_indicesNoOptional list of polygon/face indices to assign to this material slot.
material_nameYesName of the existing material in the scene.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 behavioral burden for a scene-mutating tool. It says nothing about whether overwriting an occupied slot is destructive, whether approval is required (the schema's approved field warns about a trusted approval mechanism, which the description never echoes), or whether the change is undoable.

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?

A single well-formed sentence with the core action front-loaded and the optional slot targeting appended. No wasted words, though it is arguably too terse for a six-parameter mutation tool.

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?

For a mutation tool with six parameters, no annotations, and no output schema, the description should disclose approval requirements, slot-overwrite consequences, and what the call returns or confirms. It omits all of these, leaving the agent reliant on schema field text alone.

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 all six parameters are already documented, including slot_index append behavior and the face_indices list. The description only restates slot_index at a high level and adds no syntax or semantics beyond the schema, so 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: "Assign an existing material to an object in the active scene." The word "existing" implicitly separates it from create_material and configure_material_shader siblings, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Existing material" implies a create_material step must precede this call, and the tool is scoped to the active scene, so usage context is implied rather than stated. There is no explicit when-not guidance and no named alternative for related operations.

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