Skip to main content
Glama

unreal_get_asset_thumbnail

Retrieves the thumbnail path for an Unreal Engine asset when available, enabling previews or UI display in asset workflows.

Instructions

Export asset thumbnail path when available.

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": {
      "params": "<params>"
    },
    "name": "unreal_get_asset_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does hint that the result is conditional ('when available'), but it says nothing about whether an editor connection is required, whether anything is written to disk, what image format is produced, or what happens on failure for a missing thumbnail.

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?

A single short sentence with the key qualifier ('when available') placed at the end where it matters. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

An output schema exists so return values need not be explained, but with an opaque required 'params' object and zero annotations, the description leaves the agent unable to construct a valid call. For a one-parameter lookup this should be trivially easy to document properly.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is an untyped object titled 'Params' with no documented properties. The description adds nothing about what must be supplied; an agent can only guess from the tool name that it is an asset reference.

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

Purpose3/5

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

The description names a specific resource (asset thumbnail path) but the verb is ambiguous: 'export' could mean writing a file to disk or simply returning a path string. It does not distinguish this from sibling reads such as unreal_get_asset_info, so an agent cannot tell whether the thumbnail comes bundled with other metadata.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. The only contextual clue is 'when available', which implies the thumbnail may not exist for some assets but does not tell the agent what to do in that case.

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