Skip to main content
Glama

set_bp_class_replication

DestructiveIdempotent

Set class-level bReplicates and bAlwaysRelevant on an Actor Blueprint CDO, compile it, then re-read the values to verify. Component Blueprints are refused.

Instructions

Set class-level ACTOR replication on a Blueprint's CDO (bReplicates, optionally bAlwaysRelevant), compile, and read the values back off the RE-FETCHED post-compile CDO. Actor Blueprints only: a component Blueprint is refused (component replication is set_component_replication). Related reader trap: audit_replication's class_replicates reads the ACTOR flag, so it reports false for every component Blueprint whatever its CDO says.

Returns: { blueprint_name, replicates, always_relevant_set, always_relevant } -- values re-read from the CDO after compiling; always_relevant is only present when it was requested.

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.
replicatesYesWhether the Actor class replicates to network clients. Required.
blueprint_nameNoName (or full object path) of an Actor Blueprint (must be compiled at least once).
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.
always_relevantNoSets the Actor's bAlwaysRelevant flag; only applied when the field is present

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?

Annotations already cover the safety profile (destructive, idempotent, not read-only), but the description adds genuinely new behavioral context: the tool compiles the Blueprint, re-fetches the post-compile CDO, refuses component Blueprints, and discloses that a sibling reader (audit_replication) reports misleading values for component Blueprints.

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, then adds the exclusion, the sibling-tool trap, and the return shape. Every sentence carries actionable information with no filler or repetition.

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?

With no output schema, the description supplies a Returns line describing the exact fields and the conditional presence of always_relevant. Combined with the compile side effect, refusal behavior, and the reader trap, an agent has everything needed to call and interpret it correctly.

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 every parameter including the PIE refusal behavior for `force`. The description reinforces the replicates/always_relevant semantics but adds little parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 (Set), resource (class-level ACTOR replication on a Blueprint's CDO), and the exact flags touched (bReplicates, optionally bAlwaysRelevant), plus the compile step. It explicitly distinguishes itself from set_component_replication by declaring Actor Blueprints only and refusing component Blueprints.

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?

Gives an explicit when-not rule (component Blueprints are refused) and routes the agent to the correct alternative (set_component_replication). It also warns about a related reader trap in audit_replication, which prevents misdiagnosis when checking results.

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