Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_bp_variable_replication

DestructiveIdempotent

Set a Blueprint variable's replication mode to None, Replicated, or RepNotify, then compile and create the OnRep function graph when missing.

Instructions

Set a Blueprint variable's replication mode -- None / Replicated / RepNotify (RepNotify also creates the OnRep_ function graph if missing) -- then compiles and reads CPF_Net/CPF_RepNotify back. TRAP: the full green report can come back WITHOUT the flag surviving into the generated class (a variable reported is_replicated:true that never replicates; re-running this same call fixes it). The ground truth is audit_replication (its payload's replicated_variables list), then compile and re-audit -- never this return, and never one client alone.

Returns: { blueprint_name, variable_name, mode, is_replicated, is_rep_notify, rep_notify_func, property_flags } -- read back from the variable's flags after compiling, which is necessary but NOT sufficient (see the trap above).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesOne of "None", "Replicated", "RepNotify" (case-insensitive). "None" also clears the RepNotify function and resets the lifetime condition.
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.
variable_nameYesName of a variable DECLARED on this Blueprint (inherited/native variables are refused).
blueprint_nameNoName (or full object path) of the Blueprint.
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly=false/destructive=true/idempotent=true/openWorld=false; the description adds substantial non-obvious behavior: it compiles the Blueprint, creates the OnRep function graph if missing, and documents a severe trap where a green report can return without the flag surviving into the generated class. This is rich behavioral disclosure that the annotations cannot convey.

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

Conciseness4/5

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

Purpose is front-loaded and the trap warning earns its space, but the return-value sentence is verbose and the phrase 'never one client alone' is ambiguous. Slight trimming would sharpen it without losing signal.

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, so the description carries the return contract and does so by listing every field (blueprint_name, variable_name, mode, is_replicated, is_rep_notify, rep_notify_func, property_flags) and warning that the read-back is necessary-but-not-sufficient. Nothing an agent needs to call and validate this tool is 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 goes beyond the schema by explaining the RepNotify side effect ('also creates the OnRep_<Variable> function graph if missing') and clarifying that 'None' clears the RepNotify function, adding meaning not fully carried by the mode enum.

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?

States a specific verb+resource ('Set a Blueprint variable's replication mode') and enumerates the three modes with the side effect of each (RepNotify creates the OnRep graph). An agent can tell exactly what this does versus siblings like set_bp_class_replication or set_component_replication.

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 explicit verification routing ('ground truth is audit_replication ... then compile and re-audit -- never this return') and warns not to trust a single read. However, it never states when to prefer this over the sibling replication tools (set_bp_class_replication, set_component_replication, set_replication_condition), so the when-not-versus-alternatives is only partially covered.

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