Skip to main content
Glama

add_event_dispatcher

Adds an event dispatcher (multicast delegate) and its signature graph to a Blueprint, starting with no parameters. Compile the Blueprint before broadcasting or binding nodes.

Instructions

Create an event dispatcher (multicast delegate) on a Blueprint: adds BOTH the delegate member variable and its signature graph, the way the editor's "+ Event Dispatcher" does. It starts with NO parameters -- give it a signature with set_event_dispatcher_signature. Everything downstream needs the class REGENERATED first, so compile_blueprint before add_broadcast_node (to fire it) or add_graph_node node_type="add_delegate" / add_object_bound_event (to listen).

Returns: { blueprint_name, dispatcher_name, created } -- created is always true on success; confirm with get_event_dispatchers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoOptional. This command is REFUSED while a Play-in-Editor session is running: it either compiles a Blueprint (the reinstancer can retain a world, and CheckForWorldGCLeaks is Fatal -- it KILLS the editor) or writes to disk (Editor.AllowSavingAssetsDuringPIE=0 makes the engine refuse the write, so it would report success without writing a byte). Stop PIE and retry instead; force=true runs it anyway, at your own risk.
blueprint_nameNoBlueprint asset name or path
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.
dispatcher_nameYesName of the new event dispatcher; fails if a member variable of that name already exists

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds real behavioral context beyond them: the dispatcher is created with no parameters and downstream consumers require class regeneration first. The PIE-refusal/force behavior lives only in the schema, so the description leaves a small behavioral gap here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its scope, then the immediate follow-up requirement, then the downstream ordering, then the return payload. Dense but every sentence carries distinct, actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description supplies the return shape ({ blueprint_name, dispatcher_name, created }) and a verification path via get_event_dispatchers, along with the prerequisite signature and compile steps. Complete for a creation tool of this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents blueprint_name, blueprint_path alias, dispatcher_name and the nuanced force semantics. The description only states the created dispatcher 'starts with NO parameters', which is behavior of the artifact rather than parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (Create) plus resource (event dispatcher / multicast delegate) and precise scope: it adds BOTH the member variable and its signature graph, mirroring the editor's '+ Event Dispatcher'. This differentiates it from sibling tools like remove_event_dispatcher and set_event_dispatcher_signature without needing to open schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing guidance: give it a signature with set_event_dispatcher_signature, then compile_blueprint before add_broadcast_node / add_graph_node node_type="add_delegate" / add_object_bound_event. It names concrete next-step alternatives and the ordering constraint, leaving nothing to inference.

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