Skip to main content
Glama

unreal_create_blueprint_node

Creates a Blueprint node in an Unreal Engine 5 Blueprint graph so AI clients can add logic to editor workflows.

Instructions

Create a Blueprint node.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 and discloses almost nothing. It implies a mutation (a node is added to a Blueprint graph) but says nothing about whether the Blueprint must already exist, whether the graph must be open, whether the change is undoable, or whether a compile is required afterward. This is a significant gap for a write tool with zero annotation coverage.

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 single sentence is not padded, but it is under-specified rather than concise; there is no structure, no front-loaded scope, and no detail that earns the space. Brevity here reflects missing information rather than efficiency.

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?

An output schema exists, so return values need not be explained, but for a tool whose only parameter is an opaque "params" object the description should describe the expected structure or point to a discovery tool. With no annotations and no parameter meaning, the definition is not sufficient to invoke the tool 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?

There is a single required parameter named "params" whose schema exposes no properties and 0% description coverage, so the schema tells the agent nothing about its contents. The description adds no information either — not which Blueprint, which graph, what node class, or how pins/connections are specified. The agent cannot construct a valid call from the 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 has a specific verb and resource ("Create" + "Blueprint node"), which is better than a bare name restatement. However, it does not distinguish this from siblings that also add nodes to a Blueprint graph, such as unreal_add_blueprint_event, unreal_add_blueprint_function, and unreal_add_blueprint_variable, nor does it say what kind of node (event, function call, variable get/set, macro) is created. An agent cannot tell which of these creation tools to pick.

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 mention of prerequisites (e.g., an existing Blueprint asset, a target graph), and no routing to alternatives. The agent must infer everything from sibling names alone, which the prompt explicitly says does not establish another tool's behavior.

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