Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

load_game_from_memory

Destructive

Deserialize a base64-encoded SaveGame blob into an in-memory save game instance, returning its class and path; useful for restoring or inspecting game state.

Instructions

Deserialize a SaveGame from a base64 blob (the memory_base64 of save_game_to_memory) with LoadGameFromMemory; returns the transient object save_game_instance, save_game_class and save_game_path. Invalid base64 is an error; success is false when the blob is corrupt, truncated or from another SaveGame class.

Returns: { success: bool, memory_size: int, save_game_instance: string, save_game_class: string, save_game_path: string, error: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_base64YesBase64 text of a serialized SaveGame, as returned in memory_base64 by save_game_to_memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / memory_base64 / description
      Previous value: -"Base64-encoded serialized SaveGame payload"New value: +"Base64 text of a serialized SaveGame, as returned in memory_base64 by save_game_to_memory"
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=true but give no detail; the description goes beyond them by disclosing failure semantics: invalid base64 is an error, and success is false when the blob is corrupt, truncated, or from another SaveGame class. It also notes the returned object is transient. It does not explain what the destructive hint actually means (e.g., overwriting current game state), leaving one behavioral trait implicit.

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?

Two front-loaded sentences with the return shape appended; little waste. The inline reference to the 'LoadGameFromMemory' implementation is slightly gratuitous, but overall tight and well structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description compensates by enumerating the return fields and the failure conditions, which is enough for correct invocation. The only gap is explaining the destructive behavioral implication flagged in annotations.

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 memory_base64 as the base64 text from save_game_to_memory. The description repeats this pairing but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Deserialize) and resource (a SaveGame from a base64 blob), and anchors the input to the sibling save_game_to_memory. An agent can distinguish this from load_game/load_game_async, which load from slots/files, 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 Guidelines3/5

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

It implies usage by tying the input to 'the memory_base64 of save_game_to_memory', which is useful context. However, it does not explicitly say when to prefer this over load_game or load_game_async, nor state prerequisites. Usage is implied rather than stated.

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