Skip to main content
Glama

unreal_get_character_info

Retrieves information about the selected or possessed pawn character in an Unreal Engine project, enabling AI clients to inspect character state for editing and debugging workflows.

Instructions

Get selected/pawn character 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_character_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 provided, so the description carries the full behavioral burden and largely abdicates it: it never states that the operation is read-only, what happens when nothing is selected (error vs empty result), or whether the editor must be running. An output schema exists, which relieves it of return-value detail, but the invocation preconditions remain undisclosed.

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 with no filler, so nothing is wasted, but the brevity reflects under-specification rather than discipline. The front-loaded verb is good; the sentence simply does not carry enough.

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?

Given an untyped required params object, no annotations, and no guidance, the definition is not complete enough for reliable invocation. The output schema covers return values, but selection preconditions and parameter shape are missing from both the description and the schema.

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?

There is a single required parameter "params" with 0% schema description coverage and no type information, and the description says nothing about it. With one undocumented parameter the description fails to compensate for the coverage gap, leaving the agent with no idea what to pass.

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 ... character info" gives a verb and a resource, and "selected/pawn" narrows the scope, so an agent can roughly tell this apart from siblings like unreal_get_animation_info. However, "info" is left undefined — no indication whether it covers transform, stats, class, or components — so the purpose is only minimally viable.

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 phrase "selected/pawn" hints that a character must be selected in the editor, but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as unreal_get_actor_details or unreal_get_actor_components. The agent must guess which of the many get_* tools applies.

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