Skip to main content
Glama

unreal_add_blueprint_event

Add a Blueprint event node to a Blueprint graph so AI clients can insert event-driven logic into Unreal Engine 5 projects.

Instructions

Add a Blueprint event 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_add_blueprint_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden, yet it only says 'Add'. It says nothing about whether this mutates an asset that must be pre-selected or opened, whether compilation or save is required afterward, or what happens on failure. For a mutation tool with zero annotation coverage, this is a substantial gap.

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 padding, so it is not verbose. The brevity is under-specification rather than economy, which keeps it from scoring higher.

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?

The presence of an output schema means return values need not be explained, but for a tool whose only input is an opaque required 'params' blob and which has no annotations, the description leaves too much unknown to invoke reliably. It should at minimum identify the key inputs and the target asset context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required 'params' property is an untyped object with no declared fields, so the schema gives the agent nothing. The description does not compensate at all: it never says what goes into 'params' (event name, owning Blueprint, graph, node position, event signature).

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 gives a specific verb and resource ('Add a Blueprint event node'), which is enough for an agent to know it creates an event node rather than a variable or function. It does not, however, distinguish this from close siblings like unreal_create_blueprint_node or unreal_add_blueprint_function, so differentiation is left to 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 when-to-use guidance, no prerequisite context (e.g., an existing target Blueprint), and no mention of an alternative tool for related tasks. The agent must infer the usage scenario entirely from the name.

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