UE5-MCP-Server

Overview Schema Source Related Servers Discussions Admin

ue5_get_property

Access UPROPERTY values on Unreal Engine UObjects by providing the object path and property name. For component properties, use getter functions instead.

Instructions

Gets the value of a UPROPERTY on a UObject. NOTE: Component properties (e.g., RootComponent, LightComponent) are often unavailable remotely. Use ue5_call_function with getter functions instead.

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": {
      "objectPath": "<objectPath>",
      "propertyName": "<propertyName>"
    },
    "name": "ue5_get_property"
  }
}

Input Schema

Name	Required	Description	Default
`objectPath`	Yes	The path to the UObject.
`propertyName`	Yes	The name of the property to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description reveals a key limitation: component properties are often unavailable remotely. It implies read-only behavior but could disclose more; still, it adds valuable trait beyond the schema.

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

Conciseness5/5

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

Two sentences with a clear purpose first, followed by a crucial note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple getter with 2 parameters and no output schema, the description covers the main use and a key limitation, making it complete for an agent to decide.

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

Parameters3/5

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

Schema coverage is 100%, so the description adds no additional meaning to the parameters beyond what the schema provides. Baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it gets the value of a UPROPERTY on a UObject, with specific verb+resource. The note distinguishes it from ue5_set_property and ue5_call_function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use (for component properties) and provides alternative: use ue5_call_function with getter functions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.