Skip to main content
Glama

unreal_get_mesh_materials

Retrieves the materials assigned to a mesh in Unreal Engine so you can inspect its material setup for editing or debugging.

Instructions

Get mesh materials.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether this is a read-only operation, whether the target must be an open asset, or what happens on an invalid mesh path.

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

Conciseness2/5

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

The sentence is short and front-loaded, but its brevity reflects under-specification rather than economy. No information beyond the title is conveyed, so the single clause does not earn its place as documentation.

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 need not be described, but everything else is missing: the undocumented params object, the absence of annotations, and no scope statement. For a tool whose only input is an opaque parameter bag, the definition leaves the agent unable to construct a valid call.

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?

There is one required "params" parameter with 0% schema description coverage and no nested structure, and the description says nothing about what it should contain (mesh path? asset reference? slot index filter?). The description does not compensate for the coverage gap at all.

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

Purpose2/5

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

"Get mesh materials" restates the tool name with no additional specificity. It does not say whether it returns material slot names, assigned material assets, or per-section assignments, so an agent cannot distinguish it from siblings such as unreal_get_mesh_info or unreal_get_mesh_sections beyond the literal wording of the name.

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 when-to-use guidance is given, no prerequisites, and no mention of the related sibling tools (unreal_get_mesh_info, unreal_set_mesh_material). The agent must infer usage entirely from the tool 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