Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_net_priority

DestructiveIdempotent

Write the NetPriority of an editor-world actor found by label to control replication priority when bandwidth is limited. Returns the actor name and updated priority.

Instructions

Write NetPriority, the relative replication priority when bandwidth is short, on an editor-world actor found by label. Only that placed instance changes; it is not marked dirty or saved. priority is read back after the write. Engine defaults: 1.0 for actors, 3.0 for pawns.

Returns: { actor_name, priority }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priorityYesNew NetPriority as a float, written as given with no clamping; higher makes the actor more likely to replicate when bandwidth is saturated.
actor_nameYesLabel of the actor in the editor world (matched against labels, not object names); first match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / actor_name / description
      Previous value: -"Required."New value: +"Label of the actor in the editor world (matched against labels, not object names); first match."
    • changedInput schema / properties / priority / description
      Previous value: -"float in [0.0, 10.0] (UE range)."New value: +"New NetPriority as a float, written as given with no clamping; higher makes the actor more likely to replicate when bandwidth is saturated."
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=true, idempotent=true), so the bar is lower, and the description still adds real behavior: the change is scoped to a single placed instance, it is not marked dirty or saved, and priority is read back post-write. It does not say whether the prior value is recoverable, which would have made it a 5.

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?

Front-loaded with verb, resource, and scope, then four short informative sentences with no filler. The trailing Returns line is justified because no output schema exists.

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 mutation tool with rich annotations but no output schema, it supplies the return shape, side-effect scope, and defaults. It omits error/not-found behavior and permission requirements, leaving a small gap but nothing critical for correct invocation.

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, but the description adds parameter meaning beyond the schema by giving the engine defaults (1.0 for actors, 3.0 for pawns) that an agent needs to choose a sensible value. No clamping semantics are added beyond what the schema already states.

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 (Write), the exact resource (NetPriority), and the resolution scope (editor-world actor found by label). This clearly distinguishes it from siblings like get_net_priority and set_actor_net_update_frequency without needing the schema opened.

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?

The description contextualizes the write ('only that placed instance changes; not marked dirty or saved') but never states when to reach for this tool versus siblings such as get_net_priority or the other net-configuration setters. Usage is implied by the verb/resource rather than explicitly guided.

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