Skip to main content
Glama

assign_texture

Assign an image texture to a material input using material name, image path, and optional input name; defaults to Base Color.

Instructions

Assign an image texture to a material input.

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": {
      "material_name": "<material_name>",
      "image_path": "<image_path>"
    },
    "name": "assign_texture"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYes
input_nameNoBase Color
material_nameYes

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, the description carries the full burden, and it discloses nothing about mutation effects: whether an existing texture on that input is replaced, whether shader nodes are created implicitly, or what permissions/state prerequisites exist. For a write operation this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler, but it is under-specified rather than lean; the brevity comes at the cost of necessary detail rather than from tight editing.

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?

An output schema exists, so return values need not be explained, but for a three-parameter mutation tool with zero annotation and zero schema-description coverage, the definition leaves an agent without the facts needed to invoke it correctly (prerequisites, overwrite behavior, parameter meaning).

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate; instead it names none of the three parameters. It does not explain that 'input_name' defaults to 'Base Color' or what form 'material_name' and 'image_path' take (e.g., absolute path, existing material name).

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 gives a specific verb and resource ('assign an image texture to a material input'), which is distinct from the sibling 'assign_material' that assigns a material to an object. The target (a material input) is clear, though the specific parameter vocabulary is not echoed.

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, no preconditions (e.g., the material must already exist, the image file must exist on disk), and no mention of alternatives such as creating a basic shader first. The intended usage is only implied by the sentence.

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