Skip to main content
Glama

get_asset_metadata

Read-onlyIdempotent

Fetch Asset Registry tags and core metadata (name, class, path, package) for a specific Unreal Engine asset given its path relative to /Game.

Instructions

Read an asset's Asset Registry TAGS (the indexed key/value pairs an asset publishes -- parent class, mesh stats, fork-lineage tags, ...) together with its name, class, object path and package. WARNING: its asset_name is NOT a name: the tool literally prefixes "/Game/" to whatever you pass, so it must be a path RELATIVE TO /Game ("MyGame/Systems/Foo/BP_Foo.BP_Foo"), never a bare asset name and never an absolute "/Game/..." path -- and it LOADS the asset to resolve it. Use get_assets_metadata_batch for many paths at once, get_asset_by_name for identity from a bare name, and get_assets_by_tag to search BY a tag value instead of reading the tags of one asset.

Returns: { name: string, class: string, path: string, package: string, asset_class_path?: string, package_path?: string, tags?: [{ name, value }] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_nameYesPath RELATIVE to /Game, with no leading slash (e.g. "MyGame/Systems/Foo/BP_Foo.BP_Foo"); the tool prepends "/Game/" itself, so a bare name or an absolute path both fail to resolve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive, closed-world), but the description adds real context beyond them: the tool LOADS the asset to resolve it (a side effect not implied by the annotations), and it documents the internal '/Game/' prefixing behavior and its failure mode. It stops short of discussing cost/latency of that load, which keeps it from a 5.

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?

Front-loaded with purpose, then the critical path-format warning, then alternatives, then return shape. The heavy capitalization and em-dash parentheticals make it denser and longer than necessary, but every sentence still conveys actionable information.

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?

There is no output schema, and the description compensates by spelling out the returned object shape including optional fields. For a single-parameter read tool with full annotation coverage, nothing an agent needs in order to call it is missing.

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% and its own description already states the '/Game/' prefixing rule and that bare names or absolute paths fail. The description largely restates this with emphasis, so it adds only marginal value over the structured field. Baseline 3 applies when the schema already carries the parameter semantics.

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?

States a precise verb and resource (read an asset's Asset Registry tags plus name/class/path/package) and enumerates what the tags contain. It is immediately distinguishable from sibling readers like get_asset_metadata_tags or get_asset_by_name.

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 routes the agent to three alternatives with the condition that selects each: get_assets_metadata_batch for many paths, get_asset_by_name for identity from a bare name, and get_assets_by_tag for tag-value search. No inference required.

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