Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

audit_widget_text

Read-onlyIdempotent

Sweep Widget Blueprints to find player-visible texts typed inline instead of in String Tables, so they can be given proper namespace/key identity for translators.

Instructions

Sweep Widget Blueprints and report which player-visible texts are typed INLINE rather than coming from a String Table -- the localization-maintainability question. NOTE: this corrects the intuition most people start with: a text written as a bare string is NOT lost to localization. Unreal assigns it a stable key when the package is saved, and FTextInspector::ShouldGatherForLocalization returns true, so it DOES get collected and translated. What it lacks is a MEANINGFUL identity: the namespace comes out empty and the key is an opaque GUID like 971E3B3B436AEE91028BA1ADB97B3046. That still costs -- translators see no context, and re-authoring the text churns the key, orphaning the translation. So this reports identity_kind per text: string_table (best), explicit (an author-given namespace/key), auto_key (typed inline, key generated on save) and none (never saved, no identity yet). Default output is everything that is NOT string_table or explicit.

Returns: { folder_path, widget_blueprints_scanned, texts_examined, counts_by_identity: {string_table, explicit, auto_key, none}, not_gathered_count, entries: [{ widget_bp_path, widget_name, widget_class, property_name, text, identity_kind, will_be_gathered, namespace, key, string_table }], truncated } -- not_gathered_count is the engine's own ShouldGatherForLocalization saying a text will NOT be collected at all; in a saved asset that is normally 0, and anything above it is a real alarm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recursiveNoRecurse into subfolders (default true).
folder_pathNoContent folder to sweep (default /Game). Every UWidgetBlueprint under it is loaded and walked.
include_allNoAlso report the texts that already have a good identity, string_table and explicit ones included (default false).
max_resultsNoMax Widget Blueprints to load (default 500). Loading a WBP is not free; a whole-project sweep is a heavy call.
include_data_assetsNoAlso sweep DataTables and DataAssets under the same folder (default false). This is where an AAA game actually keeps its text -- item names, quest descriptions, tooltips -- and it is text the widget walk cannot reach, because there the FTexts sit in nested struct fields rather than on a widget class. Nested structs and arrays of structs are walked too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful semantics: what each identity_kind means, that a non-zero not_gathered_count is 'a real alarm', and that loading WBPs is expensive. It doesn't cover permissions or runtime cost bounds beyond max_results, so it clears the bar but doesn't fully exploit the space.

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-loaded with the verb and resource, then progressively details identity kinds and the return shape. The long pedagogical aside about FText keys and ShouldGatherForLocalization earns its place by justifying why the audit matters, but it is bordering on over-long for a tool description.

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, yet the description spells out the return shape field-by-field (counts_by_identity, entries, truncated, not_gathered_count) and explains the alarming case. Combined with the annotations and complete schema, an agent has everything needed to call and interpret this tool 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 all five parameters are already fully documented in the schema (recursive, folder_path, include_all, max_results, include_data_assets). The description adds meaning only indirectly, by defining identity_kind values that consumption of the result depends on; it introduces no parameter syntax or defaults beyond the schema. 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 (Sweep) and resource (Widget Blueprints / player-visible texts), and frames the exact question it answers: inline vs String Table text, the localization-maintainability concern. This cleanly separates it from neighboring audits like audit_widget_accessibility and audit_widget_style.

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?

Explains the default scoping (everything NOT string_table or explicit) and points at include_all for the excluded set, so the agent knows what it will get by default. However, it gives no explicit when-to-use/when-not guidance against sibling text or asset tools (e.g. get_string_table_entries, gather_text_for_target).

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