Skip to main content
Glama

unreal_set_mesh_material

Assign a material to a specified mesh material slot in an Unreal Engine mesh, enabling targeted edits to actor or asset materials.

Instructions

Set a mesh material slot.

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_mesh_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 burden. "Set" implies mutation, but the description does not state required permissions, whether the operation is destructive or reversible, what happens to an existing material in the slot, or any side effects.

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?

The description is a single front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than disciplined conciseness. It provides no structure for understanding the operation.

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?

The tool performs a mutation with one undocumented parameter, no annotations, and a vague generic schema. Although an output schema exists and need not be explained, the description is not complete enough for an agent to invoke this correctly.

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

Parameters1/5

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

The single parameter is a generic "params" object with 0% schema description coverage. The description adds no information about what must be supplied (e.g., mesh path, slot index, material path), so the parameter is effectively undocumented.

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

Purpose3/5

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

The description names a verb and resource ("Set a mesh material slot"), which is more specific than the bare tool name. However, it does not clarify whether this assigns a material asset to a slot index, changes slot properties, or which mesh is targeted, leaving ambiguity against siblings like unreal_assign_material and unreal_set_mesh_collision.

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 prerequisites, and no distinction from alternatives such as unreal_assign_material, unreal_set_mesh_collision, or unreal_set_mesh_lod. The agent must infer the usage context entirely.

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