Skip to main content
Glama

unreal_get_blueprint

Retrieves Blueprint asset details from an Unreal Engine 5 project, enabling AI clients to inspect Blueprint structure and properties for editing and debugging.

Instructions

Get Blueprint asset details.

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_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing. 'Get' implies a read, but it never states whether the tool is non-destructive, what scope of data is returned, whether the blueprint must already be loaded, or whether missing assets error out.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally fine. The problem is under-specification rather than verbosity, so brevity here does not earn a high score.

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 that is the only thing covered. For a tool with an undocumented required parameter, no annotations, and many near-identical siblings, the description is far too thin to let an agent call it correctly.

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

Parameters1/5

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

The single parameter is an entirely opaque 'params' object with 0% schema description coverage and no defined properties. The description adds no information about what must go inside it, such as an asset path, name, or GUID, leaving the agent unable to construct a valid call from the definition alone.

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 verb ('Get') and a resource ('Blueprint asset details'), so the general action is inferable. But 'asset details' is vague about which details, and it does nothing to separate this tool from siblings such as unreal_get_animation_blueprint, unreal_get_blueprint_functions, or unreal_get_blueprint_variables.

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?

There is no when-to-use guidance at all. With over a dozen sibling 'get_blueprint_*' tools, the agent receives no signal about when to pick this general asset-details tool versus the more specific function/graph/variable/node getters.

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