Skip to main content
Glama

unreal_set_blueprint_node_property

Set a Blueprint node property in Unreal Engine to adjust node behavior or values through the MCP bridge.

Instructions

Set a Blueprint node property.

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

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 supplied, so the description carries the full disclosure burden, and it only implies mutation through the word 'Set'. It does not say whether changes require a compile or save to persist, whether the node must exist in an open Blueprint, what happens on invalid property names, or whether the operation is reversible.

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 single sentence is front-loaded and free of filler, which is good. But the brevity here is under-specification rather than economy — the sentence ends before conveying anything an agent needs.

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 this is a mutation tool with an entirely undocumented nested parameter object and no annotations. Given that the agent must guess the params structure, the definition is not complete enough to support reliable invocation.

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?

Schema coverage is 0% and the single parameter is an opaque 'params' object with no documented properties. The description adds no meaning at all — it does not reveal expected keys such as node identifier, property name, or value, so the agent cannot construct a valid call from this definition.

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 specific verb (Set) and resource (Blueprint node property), so the basic operation is identifiable. However, it gives no detail about which properties are settable and does nothing to distinguish it from the near-identical sibling unreal_set_widget_property, leaving the agent to infer scope from the name alone.

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 versus alternatives such as unreal_get_blueprint_node_details (read first), unreal_create_blueprint_node, or unreal_compile_blueprint / unreal_save_blueprint afterwards. No prerequisites, ordering, or exclusions are stated.

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