Skip to main content
Glama

unreal_get_ai_controller

Retrieves AI controller details from an Unreal Engine 5 project to inspect the controller assigned to an AI pawn or agent.

Instructions

Get AI 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_ai_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.1/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 discloses almost nothing beyond the implicit read-only nature of "Get". It does not state whether a missing or invalid AI controller yields an error or empty result, what permissions or editor state are required, or how large the returned payload is.

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 front-loaded and free of filler, but its brevity comes from under-specification rather than economy of expression. There is no structure to convey what the tool returns or what the parameter expects.

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, and the tool is conceptually simple. Even so, with a fully undocumented required parameter and no annotations, the definition leaves an agent unable to construct a correct call.

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 wrapped in an untyped "params" object with 0% schema description coverage, and the description says nothing about it. The agent has no idea whether it should pass a controller reference, a path string, or an actor name.

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?

"Get AI controller info" names a specific verb (get) and resource (AI controller), which does distinguish it from sibling unreal_get_player_controller by subject matter. However, "info" is a catch-all that doesn't say what data is retrieved (possessed pawn, rotation, state flags), so the purpose is only minimally clear.

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?

The description offers no when-to-use guidance, no prerequisites, and no indication of how it differs from unreal_get_player_controller or unreal_get_character_info. An agent must infer from the name alone that this is a read of an AI-controlled pawn's runtime data.

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