Skip to main content
Glama

set_event_dispatcher_signature

DestructiveIdempotent

Add or replace an event dispatcher's parameter list in a Blueprint you own, resolving all types before any change to prevent partial edits.

Instructions

Add to (mode="add", the idempotent default) or rewrite (mode="replace") the parameter list of a dispatcher this Blueprint OWNS -- inherited dispatchers have no local signature graph and are refused with the list of owned ones. Every requested type is resolved BEFORE anything is mutated, so a bad type aborts cleanly. The parameters become the OUTPUT pins of every bound handler and the INPUT pins of add_broadcast_node; existing nodes keep stale pins until compile_blueprint reconstructs them.

Returns: { blueprint_name, dispatcher_name, mode, added: [string], params: [ { name, type } ], param_count }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoAlias of `params` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `params`.
modeNo"add" (default, idempotent: skip a param whose name already exists) or "replace" (clear the existing signature first, then add the given params).
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.
paramsNoArray of parameter specs to add: [ { name: string, type: string } ]. Dispatcher params are input-only; 'type' accepts the same strings as add_function_parameter (bool, int, int64, float, string, name, text, byte, Vector, Array<T>, an object/class/struct/enum name or path).
args_jsonNoAlias of `params` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `params`.
parametersNoAlias of `params` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `params`.
blueprint_nameNoBlueprint asset name or path that OWNS the dispatcher (inherited dispatchers cannot be edited here).
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.
dispatcher_nameYesName of an existing event dispatcher (created by add_event_dispatcher or the editor).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing atomic type resolution before any mutation, the ownership refusal with the list of owned dispatchers, and the downstream pin effects on bound handlers and add_broadcast_node including stale pins until recompile. These are exactly the behavioral traits an agent cannot infer from destructiveHint/idempotentHint alone.

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-loads the core action and modes, then layers ownership, atomicity, and downstream effects in dense, non-redundant sentences. The trailing Returns summary is compact and earns its place.

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?

For a destructive mutation with no output schema, the description supplies the return shape, the atomicity guarantee, ownership constraints, and propagation behavior. Nothing an agent needs to invoke it safely appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by spelling out mode semantics (idempotent add vs clearing replace) and reinforcing the ownership requirement for the blueprint parameter. It does not explain the alias parameters, but the schema already does.

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?

Uses specific verbs (add/rewrite) against a well-defined resource (an event dispatcher's parameter list) and constrains it to dispatchers the Blueprint owns. An agent can distinguish this from add_event_dispatcher or reconcile_function_signature without opening the schema.

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

Usage Guidelines4/5

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

Gives clear conditions for mode='add' vs mode='replace' and explains the ownership restriction (inherited dispatchers are refused). It references related tools (add_broadcast_node, compile_blueprint) but does not explicitly route the agent away from alternative sibling tools, so it falls short of a 5.

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