Skip to main content
Glama

unreal_set_actor_scale

Sets an actor's scale in Unreal Engine 5 so AI clients can resize scene objects through the local editor bridge.

Instructions

Set actor scale.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_set_actor_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description bears the full burden, and it discloses nothing: not whether the scale is absolute or relative, whether it is world or local space, whether zero or negative scale is allowed, or whether the change requires an editor transaction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence contains no wasted words, but that is because it is under-specified rather than efficient; there is no structure that front-loads constraints or value format.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description leaves the entire input contract and all mutation behavior undocumented for what is a write operation.

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

Parameters1/5

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

There is one required parameter, a nested "params" object, with 0% schema description coverage, and the description says nothing about its fields or expected value shape. An agent has no way to know what to put inside params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Set actor scale") that is distinguishable in principle from siblings like set_actor_location or set_actor_rotation. However, it adds nothing beyond the tool name itself and never clarifies what "scale" means here (uniform vs per-axis vector).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no indication of when to use this versus unreal_set_actor_transform, which presumably can also change scale, nor any prerequisites such as level-edit mode or actor selection. Usage is only inferable from the name.

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