Skip to main content
Glama

assign_material

Attach a material to a Blender object, replacing a single existing material or adding an unused slot when multiple materials are present.

Instructions

Assign a material to an object.

An object with no material, or a single one (like the default cube's "Material"), takes the new material on every face. An object that already has several materials keeps them and gains an extra slot that no face uses yet.

Args: object_name: Name of the target object. material_name: Name of the material to assign.

Returns: Dict with the slot used and the action: "assigned", "replaced" (with the replaced material's name), "added_slot" or "already_assigned".

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

Input Schema

NameRequiredDescriptionDefault
object_nameYes
material_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 disclosure burden and does well: it explains the replacement behavior for single-material objects, the slot-adding behavior for multi-material objects, and enumerates return actions ('assigned', 'replaced', 'added_slot', 'already_assigned'). It omits permission/undo/error conditions, which keeps it short of a 5.

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 with the core action sentence, followed by behavioral detail and then Args/Returns. Well organized and mostly tight, though the parenthetical default-cube reference is slightly gratuitous.

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?

For a 2-required-parameter tool with no annotations and 0% schema coverage, the description covers both inputs, the behavioral outcome across object states, and return values. Missing only error conditions and the precondition that the material must already exist.

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 description coverage is 0%, so the Args section must compensate. It does document both parameters, but only minimally ('Name of the target object', 'Name of the material to assign'), which is barely more than the schema titles already convey. No format hints (e.g., data-block naming, whether the material must pre-exist).

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+resource ('Assign a material to an object'), which clearly separates it from siblings like create_material or set_material_property. It does not explicitly name an alternative sibling, but the action is unambiguous.

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?

The description implies when the tool is useful by explaining the three object states (no material, single material, multiple materials), which effectively tells the agent what outcome to expect. However, it never states prerequisites (e.g., the material must already exist, presumably created via create_material) nor names alternatives explicitly.

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