Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_primary_asset_id

Read-onlyIdempotent

Resolve an Unreal asset path to its Primary Asset ID (Type:Name) and split type/name fields; is_valid is false for non-primary or unscanned assets.

Instructions

Look up the registered Primary Asset Id ("Type:Name") of an asset path: primary_asset_id, is_valid and, when valid, primary_asset_type and primary_asset_name. A non-primary or unscanned asset gives is_valid=false, not an error. get_primary_asset_id_from_path is the same lookup without the split fields.

Returns: { asset_path, primary_asset_id, is_valid, primary_asset_type, primary_asset_name }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_pathYesFull object path including the object name, e.g. /Game/MyGame/M_Example.M_Example; a package-only path does not match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / asset_path / description
      Previous value: -"Object path, e.g. /Game/MyGame/M_Example.M_Example"New value: +"Full object path including the object name, e.g. /Game/MyGame/M_Example.M_Example; a package-only path does not match."
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful edge-case context beyond them: a non-primary or unscanned asset yields is_valid=false rather than an error, and it discloses the exact result shape.

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 compact sentences plus a return signature, all front-loaded with the core purpose before the sibling distinction and the return shape. Every element earns its place.

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, but the description enumerates the returned fields explicitly, and the edge-case semantics plus sibling differentiation make it fully sufficient for a single-parameter lookup.

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 schema already explains asset_path fully (including the package-only-path caveat). The description adds no syntax beyond that, so the baseline 3 is appropriate.

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 specific verb ('Look up') and resource (the registered Primary Asset Id of an asset path), and explicitly distinguishes itself from the sibling get_primary_asset_id_from_path. An agent can tell the two apart without opening either schema.

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?

It names the direct alternative (get_primary_asset_id_from_path) and the condition that differentiates it ('without the split fields'), plus the non-error behavior for unscanned assets. It stops short of covering the broader sibling set (e.g. get_primary_asset_ids_by_type), so it's clear but not exhaustive.

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