Skip to main content
Glama

unreal_get_material

Retrieve material details from an Unreal Engine 5 project so you can inspect shader parameters, textures, and settings before editing materials or debugging rendering issues.

Instructions

Get material details.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/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: no read-only confirmation, no statement of what identifier the single params argument takes, no permission or error behavior. The one sentence merely restates the title.

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?

It is short, but brevity here comes from under-specification rather than economy; the single four-word sentence is merely a placeholder. There is no front-loaded scope or usage signal an agent could act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists (so return values needn't be explained), the description never says what input identifies the material or what is returned in kinds of terms. For a read tool with an entirely undocumented params object and no annotations, the definition is not sufficient to invoke it 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?

One required parameter ("params") with 0% schema description coverage and no type or property information, made worse by the description offering zero clarification of what that opaque object should contain. Both the schema and the description leave the caller unable to construct a valid call.

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 material details" restates the tool name with a vague noun ("details") and never says which details, so it cannot be distinguished from the sibling unreal_get_material_parameters or from other material readers. The verb+resource is present, but the scope is undefined.

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, no exclusions, and no mention of alternatives such as unreal_get_material_parameters or unreal_get_asset_info. An agent must infer from the name alone whether this reads parameters, a graph, or metadata.

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