Skip to main content
Glama

unreal_set_material_parameter

Set a material instance parameter to adjust material appearance or behavior in Unreal Engine 5 projects.

Instructions

Set a material instance parameter.

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": {
      "params": "<params>"
    },
    "name": "unreal_set_material_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

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?

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing beyond the mutation implied by 'set'. It omits whether the target instance must exist, whether changes are persistent without unreal_save_material, whether a recompile is triggered, or what errors occur on unknown parameter names.

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?

It is a single clean, front-loaded sentence with no waste, but its brevity comes from under-specification rather than economy of expression.

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 needn't be explained, but for an unannotated mutation tool whose only argument is an opaque object, the description leaves far too much unknown. An agent cannot reliably construct the params payload or predict side effects from this definition alone.

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?

The single required parameter is an untyped 'params' object with 0% schema description coverage, and the description does not name or explain any expected fields such as parameter name, value, or material path. The word 'parameter' hints at a name/value payload but adds no usable meaning beyond the schema.

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 a specific verb ('Set') and a specific resource ('material instance parameter'), which is more precise than the bare tool name and distinguishes it from mesh-level or node-level siblings like unreal_set_mesh_material. It does not explain how it differs from unreal_set_niagara_parameter or unreal_get_material_parameters, but the operation itself 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as unreal_set_mesh_material or unreal_assign_material, nor any stated preconditions (existing instance, compiled material). An agent must infer the usage context entirely from the name.

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