Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

manage_material_authoring

Create and manage Unreal Engine materials with expressions, parameters, functions, instances, and landscape blend layers.

Instructions

Create materials with expressions, parameters, functions, instances, and landscape blend layers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoNode X position.
yNoNode Y position.
codeNoCode or expression.
nameNoName identifier.
pathNoDirectory path for asset creation.
saveNoSave the asset(s) after the operation.
groupNoGroup name.
valueNoValue to set (number, vector object, or texture path).
actionYesMaterial authoring action to perform. Use create_complete_material to create a full material with expressions and connections in a single call.
constANoConstant A input value.
constBNoConstant B input value.
layersNoArray of layer configurations for layer blend.
nodeIdNoID of the node.
pinNameNoName of the pin.
uTilingNoU tiling factor.
vTilingNoV tiling factor.
twoSidedNoEnable two-sided rendering.
assetPathNoAsset path (e.g., /Game/Path/Asset).
blendModeNoBlend mode.
blendTypeNoLandscape layer blend type.
inputNameNoName of the input.
inputTypeNoType of function input/output.
layerNameNoName of the layer.
operationNoMath operation type.
sourcePinNoSource pin name (output).
targetPinNoTarget pin name (input).
outputTypeNoOutput type of custom expression.
propertiesNoAdditional material properties to set via console commands, e.g. {bUsedWithSkeletalMesh: true} (for create_complete_material)
connectionsNoArray of connections between expressions and material inputs (for create_complete_material)
descriptionNoDescription for custom expression or function.
expressionsNoArray of expressions to add to the material (for create_complete_material)
samplerTypeNoTexture sampler type.
texturePathNoTexture asset path.
defaultValueNoDefault value for parameter (number for scalar, object for vector, bool for switch).
functionPathNoPath to function asset.
shadingModelNoShading model.
sourceNodeIdNoSource node ID for connection.
targetNodeIdNoTarget node ID for connection.
parameterNameNoName of the parameter.
materialDomainNoMaterial domain type.
parentMaterialNoPath to parent material for instances.
coordinateIndexNoUV channel index (0-7).
exposeToLibraryNoExpose function to material library.
Behavior2/5

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

Annotations are all false, providing no safety or mutation cues. The description says 'create' but doesn't disclose side effects like overwriting assets, whether existing materials are modified, or any prerequisites. No additional behavioral context is provided.

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 a single sentence, front-loads the primary verb, and lists key features without redundancy. It is appropriately concise for an overview, though it sacrifices completeness.

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?

Given 43 parameters and 39 actions, the one-sentence description is far too sparse. It doesn't mention the create_complete_material convenience action, editing existing materials, or the distinction between creating assets vs connecting nodes. No output schema exists, so the description should explain more about return values or side effects.

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 descriptions cover 100% of parameters, so baseline is 3. The tool description lists high-level categories (expressions, parameters, functions, instances) but doesn't add meaning beyond what the schema already provides. No new parameter insight.

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 states the tool creates materials with specific components (expressions, parameters, functions, instances, landscape blend layers), clearly identifying the resource and differentiating from sibling asset tools. However, it omits many actions from the enum like set_blend_mode, connect_nodes, and compile_material, so it underrepresents the full purpose.

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?

No guidance on when to use this tool vs alternatives such as manage_asset or manage_texture, nor when to use create_complete_material versus individual node actions. The description only states what the tool does, not when to choose it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flux-Point-Studios/unreal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server