Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

link_montage_sections

DestructiveIdempotent

Link an Unreal montage section to the next by setting its NextSectionName, since add_montage_section does not connect sections. Pass an empty or None value to clear the link.

Instructions

Chain one montage section to the next by setting its NextSectionName. add_montage_section creates sections but never links them; this writes FCompositeSection::NextSectionName so playback flows section -> next. Pass next_section_name "" or "None" to clear the link. Done in an undo transaction, then saved. Idempotent: the link the section already has is a success with changed=false and saved=false, and the montage is neither modified nor saved. A failed save makes success false, with saved=false and save_error.

Returns: { montage_path, section_name, next_section_name, linked, changed, section_count, sections, saved, save_error, message }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
montage_pathYesFull asset path of the montage (e.g. '/Game/MyGame/AM_Example').
section_nameYesName of the existing section whose link to set.
next_section_nameYesName of the existing section to play next (or "" / "None" to clear).

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?

Goes well beyond annotations by disclosing that the write happens in an undo transaction then a save, exactly what idempotency yields (changed=false, saved=false, no modification), and the failure semantics (success=false, saved=false, save_error). This is concrete side-effect and failure-mode context that annotations alone (idempotentHint, destructiveHint) do not 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?

Front-loads the core action and the sibling contrast before the behavioral details. The trailing return-shape line is slightly redundant given no output schema, but the prose is dense and each sentence carries meaning.

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 3-param mutation with no output schema, the description covers side effects, idempotency, save behavior, clearing semantics, and even the return fields. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already documents all three parameters including the "" / "None" clear convention, so the description largely restates it. It adds only light reinforcement that next_section_name must be an existing section; 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 and resource ('chain one montage section to the next') and immediately names the underlying field it writes (NextSectionName). It explicitly contrasts with sibling add_montage_section, so an agent can distinguish them without opening either schema.

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?

Names the alternative (add_montage_section creates but never links) and the condition that selects this tool, plus the special clearing case via "" / "None". Routing is unambiguous.

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