Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

set_material_expression_property

Modify a property of any material expression node in Unreal Engine. Use common property names like parameter_name, default_value, or texture to update the node's settings.

Instructions

Set a property on an existing material expression node.

Accepts snake_case ("parameter_name") or PascalCase ("ParameterName").

Common properties: parameter_name, default_value, slider_min, slider_max, group, texture, code, description, output_type, inputs, add_inputs, outputs, SpeedX, SpeedY, CoordinateIndex, R, Constant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_indexYes
material_pathYes
property_nameYes
property_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds value by noting that it accepts both snake_case and PascalCase naming, which is a helpful behavioral detail. However, with no annotations, it does not disclose error handling, side effects, or return values beyond what output schema might cover.

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?

The description is concise with two sentences and a bullet-like list of common properties. It is front-loaded with the purpose and provides additional detail without being verbose.

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 tool with 4 parameters and zero schema coverage, the description is incomplete. It fails to explain material_path and node_index, and does not specify the format or constraints of property_value. The output schema exists but is not reflected in the description.

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%, yet the description only provides examples for property_name, ignoring material_path, node_index, and property_value. It does not sufficiently compensate for the lack of schema descriptions.

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 clearly states the tool sets a property on an existing material expression node. It distinguishes from siblings like add_material_expression and set_material_instance_parameter by specifying 'existing expression node'.

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 versus alternatives, no prerequisites mentioned, and no exclusions or caveats provided.

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/aadeshrao123/Unreal-MCP'

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