Skip to main content
Glama

unreal_set_viewport_mode

Set viewport mode and show flags in Unreal Engine where supported. Use it to control editor viewport display settings through the MCP bridge.

Instructions

Set viewport mode/show flags where supported.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it delivers almost nothing: no indication of what gets changed or destroyed, whether the change persists, what permissions or editor state are required, or what happens when the mode is unsupported. The "where supported" clause actually introduces an undisclosed failure mode the agent cannot reason about.

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?

One short, front-loaded sentence with no filler or repetition. It is concise, but the brevity reflects under-specification rather than disciplined editing.

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?

Placeholder.

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 free-form "params" object with no properties defined. The description adds no information about what belongs in params, so an agent has no way to construct a valid invocation from the definition.

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?

"Set viewport mode/show flags" gives a verb and a partial resource, so the agent can tell this touches viewport display state rather than camera transform or game mode. But "mode/show flags" is undefined terminology and "where supported" hedges the scope, so it does not clearly separate this from siblings like unreal_set_game_mode or unreal_set_viewport_camera.

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 statement of when to use this tool, when not to, or which sibling to prefer for viewport display changes. "Where supported" hints that applicability is conditional but never says what the condition is or how the agent should check it.

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