Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

copy_anim_graph_nodes

Copies AnimGraph nodes with settings and wiring between graphs, preserving struct properties and within-selection links, then saves the blueprint; recompile for runtime effect.

Instructions

Copy a set of AnimGraph nodes (with internal FAnimNode settings + intra-selection wiring) between graphs. Equivalent to the editor's copy/paste: preserves each node's runtime struct properties and any links WITHIN the copied set (links to nodes outside the selection are dropped). Saves the destination ABP but does NOT recompile it -- run compile_anim_blueprint after your edits for runtime effect.

Returns: { copied_count, id_map:{old->new}, imported_nodes[], missing_node_ids[], saved }

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.
node_idsYesArray of source NodeGuid strings (from get_graph_nodes) to copy.
offset_xNoX offset added to every pasted node (optional, default 0).
offset_yNoY offset added to every pasted node (optional, default 0).
dst_graphNoDestination graph name (optional, default the top-level AnimGraph).
src_graphNoSource graph name (optional, default the top-level AnimGraph).
dst_anim_blueprint_pathYesDestination UAnimBlueprint path/name.
src_anim_blueprint_pathYesSource UAnimBlueprint path/name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses exactly what is preserved (runtime struct properties, intra-selection wiring), what is dropped (links to nodes outside the selection), and the critical side effect that the destination ABP is saved but NOT recompiled. The force-param schema even documents the PIE refusal. This is unusually rich behavioral disclosure for a mutation tool.

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?

Three tight sentences, each carrying distinct information, with the core copy semantics front-loaded and the return shape appended. No filler or restatement of the name.

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 an 8-param mutation tool with no output schema, the description supplies the missing return shape (copied_count, id_map, imported_nodes, missing_node_ids, saved), the side-effect profile, and the required follow-up step. Nothing an agent needs to invoke it correctly is absent.

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 all eight parameters are already documented in the schema, including the detailed force/PIE warning. The description's discussion of the 'copied set' indirectly enriches node_ids, but it adds no syntax or format detail beyond the schema, so the baseline 3 is 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 (Copy) and resource (a set of AnimGraph nodes) with clear scope (between graphs). The parenthetical immediately clarifies what travels with the copy, so an agent understands this is not a shallow duplicate.

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 strong workflow context by naming the required follow-up ('run compile_anim_blueprint after your edits for runtime effect'), which is essential for correct sequencing. It does not name a when-not condition or a competing sibling, but no direct alternative exists in the sibling list, so the guidance is effectively complete.

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