Skip to main content
Glama

unreal_set_actor_visibility

Sets an Unreal Engine actor's visibility so AI clients can show or hide scene objects during editor workflows.

Instructions

Set actor visibility.

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_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing beyond the bare action. For a mutation tool it says nothing about required actor references, persistence of the change, reversibility, or whether hiding affects collision/gameplay.

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 is terse but the brevity is under-specification rather than efficiency; there is nothing front-loaded beyond a restated name.

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

Completeness1/5

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

With an opaque required "params" object, no annotations, and no parameter documentation, the definition is far too thin for a mutation tool. The presence of an output schema excuses only return-value explanation, not the missing input and behavioral detail.

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?

Schema description coverage is 0% and the single required parameter is an untyped "params" object. The description adds no explanation of what must go inside it (actor identifier, boolean flag, etc.), so an agent cannot construct a valid call from the definition alone.

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 names a specific verb and resource ("Set actor visibility"), so the basic intent is graspable. However, it never clarifies what "visibility" means in this context (render visibility, editor-hidden flag, per-player visibility) nor how it differs from the sibling unreal_manage_level_visibility, leaving real ambiguity.

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 when-to-use guidance at all: no preconditions, no note about when to prefer this over unrelated sibling setters or the level-visibility tool. Only the tool name implies its place in the workflow.

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