Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

get_actor_property_metadata

Inspect metadata for properties on a placed Unreal actor, including type, clamp, enum values, and category. Returns a structured summary to navigate properties without flooding context.

Instructions

Inspect type/clamp/enum metadata for properties on a placed actor.

Returns a flat dict keyed by dotted path with per-property metadata (cpp_type, ue_type, category, display_name, tooltip, current_value, clamp_min/max, ui_min/max, valid_values for enums, inner/element/key/value types for containers, object_class / meta_class for refs, plus is_struct/is_array/is_enum/is_object /is_bool / editable / transient / readonly flags).

ALSO returns a "_summary" header containing total_available, total_returned, truncated, next_cursor, own_count, inherited_count, class_chain, and a "categories" map (UPROPERTY Category -> count) — use this to navigate without flooding context. max_entries=0 returns ONLY the summary so you can plan first.

Args: actor_label: Outliner label or UObject name. property_path: Optional dotted path. Empty = enumerate top-level properties. If the path is a struct, enumerates that struct's fields. If a leaf scalar/enum, returns metadata for just that property. If an OBJECT REFERENCE, returns single-property metadata for the ref + a hint (use component_name to inspect the target's properties), unless descend_into_objects=True is passed. filter: Case-insensitive substring on full dotted path. category: Case-insensitive exact match against UPROPERTY(Category="X"). Sub-categories use "|" — e.g. "Lens|Bloom". depth: How many struct levels to expand below the start point. 0 = flat. expand_enums: Include valid_values list for enum-typed fields. include_inherited: Include properties from super classes. False = only those declared on the most-derived class (use to scope down components). descend_into_objects: When property_path lands on an FObjectProperty, enumerate the target object's class instead of returning a single metadata blob. Disabled by default — prefer component_name. max_entries: Hard cap on emitted entries. Default 50. 0 = summary only. Pair with cursor for pagination. cursor: Pagination offset. Use _summary.next_cursor from the previous response to fetch the next page. component_name: Optional. Anchor target object to a named component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
cursorNo
filterNo
categoryNo
actor_labelYes
max_entriesNo
expand_enumsNo
property_pathNo
component_nameNo
include_inheritedNo
descend_into_objectsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It thoroughly discloses behavior: what is returned (flat dict with metadata, _summary with pagination info), effects of parameters like descend_into_objects and max_entries=0, and no destructive actions implied.

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

Conciseness4/5

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

Well-structured with a clear purpose statement upfront, followed by output explanation and parameter details. Slightly verbose but every sentence adds value; could be slightly more concise but still efficiently organized.

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?

Given the tool's complexity (11 parameters, output schema present), the description is highly complete. It covers all parameters, return values, and pagination, fully addressing the agent's needs for correct invocation.

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

Parameters5/5

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

Despite 0% schema description coverage, the description adds extensive meaning to each parameter, explaining how they affect output (e.g., property_path navigation, filter, depth, pagination). Complements the schema effectively.

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?

Description clearly states 'Inspect type/clamp/enum metadata for properties on a placed actor' with a specific verb and resource. It distinguishes from sibling tools that operate on other aspects like assets, materials, or Niagara systems.

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

Usage Guidelines4/5

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

Provides detailed usage scenarios for different parameter values (e.g., empty property_path, struct, object reference) and explains the _summary header for pagination. Does not explicitly state when not to use, but the specificity makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadeshrao123/Unreal-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server