Skip to main content
Glama

unreal_get_viewport_info

Retrieves viewport camera information from Unreal Engine 5 so you can check camera position, rotation, and view settings before editing or capturing a level.

Instructions

Get viewport camera info.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden and largely drops it. 'Get' weakly implies a non-mutating call, but nothing is said about editor-session requirements, whether the viewport must be focused, or failure modes in headless/commandlet contexts.

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

Conciseness3/5

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

It is a single short sentence with the verb and resource front-loaded, so there is no wasted wording. Brevity here tips into under-specification rather than efficiency, since nothing substantive follows the lead clause.

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 described, which relieves part of the burden. Still, for a tool whose only input is an undocumented params object and which has no annotations, the description leaves the agent guessing about both invocation and read-only behavior.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'params' property is an untyped object, so the schema explains nothing. The description adds no information about what may go inside params — an empty bag, a camera index, or viewport selection — leaving the one required argument fully opaque.

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 pairs a specific verb ('Get') with a specific resource ('viewport camera info'), which separates it from the set_* siblings such as unreal_set_viewport_camera. However, 'info' is left undefined — it does not say whether the result is camera transform, FOV, projection mode, or all of them, so the agent cannot tell exactly what it retrieves.

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 whatsoever: no mention of when to prefer this over unreal_get_world_info or unreal_capture_viewport, and no note of prerequisites such as an open editor viewport. The only signal is the implicit 'get' versus 'set' split in 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