Skip to main content
Glama

material_wire_texture_set

Wire textures into an Unreal Engine Material graph by setting BaseColor, Normal, ORM (Roughness/Metallic/AO), and Emissive inputs. Empty texture paths are ignored.

Instructions

Wire a standard texture set into a Material graph.

ORM textures are assumed to pack Occlusion in R, Roughness in G, and Metallic in B. Empty texture paths are ignored.

Args: material_path: Material asset path base_color_texture: Texture path wired to BaseColor normal_texture: Texture path wired to Normal orm_texture: Packed ORM texture path wired to AO/Roughness/Metallic emissive_texture: Texture path wired to EmissiveColor compile: Force a material shader compile before returning save: Save the material package immediately

KB: see knowledge_base/08_MATERIALS_AND_RENDERING.md#overview Example: material_wire_texture_set(material_path="/Game/MCP_Test/M_Example")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNo
compileNo
orm_textureNo
material_pathYes
normal_textureNo
emissive_textureNo
base_color_textureNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the non-obvious ORM channel assumption (R/G/B), states that empty texture paths are ignored, and clarifies what compile/save flags do. It does not discuss overwriting existing pin connections or default persistence, but the main side-effect surface is covered.

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

Conciseness5/5

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

The description is tightly organized: purpose, key assumption, parameter semantics, KB pointer, and example. Every section earns its place, and the most decision-relevant facts are front-loaded.

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

Completeness5/5

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

For a mutation tool with seven parameters and no annotations, the description is complete enough to call correctly: all parameters are explained, non-obvious packing behavior is documented, an example is supplied, and a KB reference exists. An output schema also exists, so return-value documentation is not required here.

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

Parameters5/5

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

Schema description coverage is 0%, yet the Args block documents all seven parameters with graph-target semantics: each texture path is mapped to BaseColor, Normal, AO/Roughness/Metallic, or EmissiveColor, and compile/save behavior is specified. The example and ORM detail add practical meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line uses a specific verb and resource: 'Wire a standard texture set into a Material graph.' This clearly identifies the operation and, together with the ORM channel note, sets it apart from generic material-creation or expression-wiring siblings.

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 intended scenario is implied by 'standard texture set' and the ORM packing note, and the KB link offers further context, but the description never explicitly states when to choose this over mat_connect_expressions, material_set_instance_parameters_bulk, or other material tools. There are no exclusions or alternative-routing statements.

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