Skip to main content
Glama

unreal_get_material_parameters

List material parameters for an Unreal Engine material to inspect available inputs and support adjusting material behavior.

Instructions

List material parameters.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List" weakly implies a read-only operation, but nothing is said about whether the material must exist, whether parameters come from the instance or base material, or whether results are grouped/cached.

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 but that brevity reflects under-specification rather than economy of expression. There is no structure, no leading constraint, and no content beyond a restated name.

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 explained, but the input side is opaque: a required "params" object with zero documented structure. For a tool whose only job is to be invoked correctly, the description 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?

The single required parameter is named only "params" with 0% schema description coverage and no type information, and the description says nothing about it. An agent cannot determine what to pass (a material path? an object reference? nested fields?) from either source.

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?

"List material parameters" essentially restates the tool name (get_material_parameters) with no added specificity. It never says which material's parameters, what a parameter is in this context (scalar/vector/texture), or how it differs from unreal_get_material or unreal_get_niagara_parameters.

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 (e.g. material must be loaded/selected), and no reference to alternatives such as unreal_get_material for the asset itself or unreal_set_material_parameter for mutation. The agent is left to infer usage 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