Skip to main content
Glama

get_asset_streaming_config

Read-onlyIdempotent

Read Unreal texture streaming settings: global streaming pool size, or one asset's NeverStream flag, LODGroup, and virtual texture priority.

Instructions

Read the streaming knobs (inverse of configure_asset_streaming). Works at two levels: with NO asset_path it reports the GLOBAL texture-streaming pool size (only when the editor runs a render-asset streaming manager -- an editor started with -nullrhi has none, and then streaming_manager_available is false and the pool size is omitted); with one, it adds that asset's NeverStream flag (which applies to any UStreamableRenderAsset -- textures AND static meshes) plus the texture-only LODGroup and VirtualTextureStreamingPriority. There is NO streaming_priority field -- see the note below.

Returns: { streaming_manager_available: bool, global_pool_size?: int, asset_path?, asset_class?, is_streamable?: bool, never_stream?: bool, lod_group?: string, lod_group_int?: number, use_virtual_texture_streaming_priority?: bool, note? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_pathNoOptional /Game/... asset path; if omitted, returns global streaming config only

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 declare read-only/idempotent/non-destructive, and the description adds genuine behavioral context beyond them: the -nullrhi case where streaming_manager_available is false and the pool is omitted, and that never_stream applies to both textures and static meshes. The dangling 'see the note below' reference (no note appears) is a minor flaw.

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?

Purpose is front-loaded and the two-level semantics are laid out in order, but the dense parentheticals and the unresolved 'see the note below' add mild clutter.

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

Completeness4/5

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

No output schema exists, but the description inlines the full return shape including conditional fields, which covers what an agent needs. The forward reference to a note that isn't present is the one completeness gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning: asset_path selects between global and per-asset behavior and changes which fields are returned. It also clarifies there is no streaming_priority field, pre-empting a wrong assumption.

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 ('Read') and resource ('streaming knobs') and explicitly positions itself as the inverse of configure_asset_streaming, letting an agent separate it from a sibling without opening the 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?

Clearly explains the two invocation modes (no asset_path = global pool; with asset_path = per-asset flags), which is real when-to-use guidance. It doesn't explicitly exclude alternative tools like get_asset_lod_settings or get_render_settings, so no full 5.

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