Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_actor_label

DestructiveIdempotent

Rename an editor-world actor's outliner label by matching its internal name or current label; invalid or empty labels are ignored, so verify the returned label.

Instructions

Set the outliner label of an editor-world actor found by internal name or current label (first match). The engine trims it and keeps the old label when the new one is invalid, for example empty, so check label in the reply. Marks the level dirty without an undo entry.

Returns: { actor_name: string, label: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_labelYesDisplay label to set, e.g. "Lamp_Kitchen"; leading and trailing spaces are trimmed.
actor_nameYesCurrent actor name or label in the world outliner

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / new_label / description
      Previous value: -"New label to apply"New value: +"Display label to set, e.g. \"Lamp_Kitchen\"; leading and trailing spaces are trimmed."
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations mark it as a non-idempotent-safe mutation, but the description adds real behavior beyond them: the engine trims whitespace, retains the old label when the new one is invalid (e.g. empty), marks the level dirty, and creates no undo entry. That no-undo warning and partial-failure semantics are exactly what an agent needs before mutating.

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 sentences plus a return shape, front-loaded with the mutation target, then side effects, then return. Every clause carries operational weight; nothing is boilerplate.

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 the return shape itself, plus lookup semantics, failure semantics, and side effects. An agent has everything needed to call and verify this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by resolving the matching ambiguity of actor_name ('first match' when name or label collide) and restating the trimming rule as an engine guarantee rather than a suggestion.

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+resource (set the outliner label of an editor-world actor) and qualifies the lookup precisely: found by internal name or current label, first match. An agent can distinguish this from sibling get_actor_label or set_actor_folder without opening any 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 gives invocation guidance ('found by internal name or current label', 'check label in the reply') and failure context, but never states when this tool should be chosen over alternatives, nor any exclusions or prerequisites. Usage is implied rather than directed.

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