Skip to main content
Glama

unreal_connect_material_nodes

Connects material expression nodes in Unreal Engine material graphs, letting AI clients wire inputs and outputs to build or edit materials.

Instructions

Connect material expressions.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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. 'Connect' implies a mutation of the material graph, but the description does not say whether the connection is persisted, whether inputs must be free, whether it requires an open material editor, or what happens when the connection is invalid. Only the bare minimum mutation implication is conveyed.

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?

Three words with no padding, but the brevity comes from under-specification rather than discipline. There is no structure beyond a single fragment, and nothing is front-loaded other than the verb.

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?

For a mutation tool with an opaque one-parameter schema, zero annotations, and 0% schema coverage, the description should explain the parameter shape and the effect on the material graph. An output schema exists so return values need not be described, but the input contract and behavioral effects remain undocumented.

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 an untyped 'params' object with zero description coverage and no listed properties, so the schema explains nothing. The description likewise says nothing about what must be passed in (which expressions, which pins), leaving the parameter entirely opaque.

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 and resource ('Connect' + 'material expressions'), making the operation itself unambiguous. It falls short of a 5 because it offers no differentiation from the closely-named sibling unreal_connect_blueprint_nodes, and no detail on what kinds of expressions are connected.

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 rather than unreal_connect_blueprint_nodes or when to use unreal_disconnect_material_nodes. The agent must infer from the tool name alone that this applies specifically to material graphs.

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