Skip to main content
Glama
miracle1814

ue5-automation

by miracle1814
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ue5_read_blueprint

Reads Unreal Engine Blueprint assets to inspect class info, variables, CDO, node graphs, and pin connections. Returns structured JSON for safe, read-only analysis.

Instructions

Read a Blueprint asset: level L1 = class info + variables + CDO, L2 = node graph + connections, full = both. Read-only and safe to call any time. Returns structured JSON (Markdown/Mermaid reports available via the CLI reader). | 读取蓝图（L1 类信息+变量+CDO / L2 节点+连线 / full）。

Input Schema

NameRequiredDescriptionDefault
levelNoL1 | L2 | full (default L1) | 读取层级
fieldsNoKeep only these node/connection fields, e.g. ['title','guid','pos'] | 只返回指定字段（省 token）
include_cdoNoInclude class-default-object values | 是否包含 CDO
blueprint_pathYesBlueprint asset path, e.g. /Game/BP_Test | 蓝图资产路径
include_connectionsNoInclude pin connections | 是否包含连线

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.5.4
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keep only these node/connection fields, e.g. ['title','guid','pos'] | 只返回指定字段（省 token）",
+  "type": "array"
+}
  2. Changed4 schema fields changedv3.2.1
    • addedInput schema / properties / blueprint_path / description
      Added value: +"Blueprint asset path, e.g. /Game/BP_Test | 蓝图资产路径"
    • addedInput schema / properties / include_cdo / description
      Added value: +"Include class-default-object values | 是否包含 CDO"
    • addedInput schema / properties / include_connections / description
      Added value: +"Include pin connections | 是否包含连线"
    • addedInput schema / properties / level / description
      Added value: +"L1 | L2 | full (default L1) | 读取层级"
  3. First observedv3.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does so reasonably: it states the tool is read-only and safe to call any time, and it says it returns structured JSON. It does not discuss performance or output shape in depth, but for a read-only tool the key safety profile is covered.

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?

The description is front-loaded and appropriately sized, with the level semantics stated before the read-only note and return format. The repeated Chinese translation adds some redundancy without new information, keeping it from a 5.

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?

Given no output schema and no annotations, the description supplies the important context: level meanings, read-only safety, and JSON return format. It stops short of describing the exact JSON shape, but the level breakdown gives enough structure for an agent to call it correctly.

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 the baseline is 3. The description adds useful meaning beyond the schema by defining what each level value contains (L1 class info/variables/CDO, L2 node graph/connections, full both), which is central to invoking the tool correctly.

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

Purpose4/5

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

The description names a specific verb and resource ('Read a Blueprint asset') and explains the level-based scope (L1 class info/variables/CDO, L2 node graph/connections, full). It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as ue5_read_nodes or ue5_read_connections, which overlap with L2.

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

Usage Guidelines3/5

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

The description implies usage through the level definitions and states it is safe to call any time, but it does not say when to choose this tool over alternatives like ue5_read_nodes or ue5_read_connections. The agent must infer the appropriate context from the level descriptions alone.

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