Skip to main content
Glama

unreal_get_player_controller

Retrieves the player controller's details from an Unreal Engine 5 project so AI clients can inspect and act on the active player controller during editor workflows.

Instructions

Get player controller 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_player_controller"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden, yet it says nothing about whether the call requires a running editor session, what happens if there is no player controller (null vs. error), or whether the operation has any side effects. The 'Get' prefix implies read-only, but that is inference rather than disclosure.

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?

One short sentence that is front-loaded and free of waste, but its brevity comes from omission rather than efficiency. There is no structure to speak of and nothing beyond the bare noun phrase.

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?

Return-value explanation is legitimately not needed because an output schema exists, which carries much of the disclosure burden for a simple getter. What remains missing is the input contract and any environmental precondition, so the definition is serviceable for identification but not for correct invocation.

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 required parameter is an untyped 'params' object with no declared properties or enum values. The description offers no compensating detail about what must go inside params (player index, controller reference, world context), so an agent cannot construct a valid call from the text.

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 verb ('Get') and a resource ('player controller'), so the general target is identifiable and is distinguishable from nearby siblings like unreal_get_ai_controller. However, 'info' is a placeholder rather than a statement of what is retrieved (transform, possessed pawn, input state, etc.), leaving the purpose only vaguely specified.

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, no preconditions, and no mention of any alternative such as unreal_get_ai_controller or unreal_get_character_info. The agent must infer the selection criteria entirely from the tool 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