Skip to main content
Glama

unreal_get_blueprint_graphs

List Blueprint graphs in an Unreal Engine 5 project so you can inspect graph structure before editing or debugging Blueprint logic.

Instructions

List Blueprint graphs.

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

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 behavioral burden, yet it only implies a read/list operation. It says nothing about permissions, editor vs. asset-registry state, whether the Blueprint must be loaded/open, or how many graphs come back.

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?

The single short sentence is front-loaded and free of padding, but its brevity comes at the cost of under-specification rather than efficiency. Nothing is wasted, but very little is delivered.

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 described, but the required opaque params object is left entirely unexplained. For a tool that presumably needs a Blueprint identifier or path to scope the listing, the definition is not complete enough to invoke confidently.

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 required parameter "params" has 0% schema description coverage and no type or property definition, and the description adds no explanation of what belongs inside it. With one undocumented, structurally undefined parameter, the description does nothing to compensate for the schema gap.

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?

"List Blueprint graphs" gives a verb (List) and a resource (Blueprint graphs), so an agent can guess it enumerates graph assets rather than nodes or variables. However, it is nearly a restatement of the tool name and states no scope — which Blueprint, all Blueprints, or filtered by the params object.

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 guidance on when to use this versus the many sibling blueprint readers such as unreal_get_blueprint, unreal_get_blueprint_nodes, or unreal_get_blueprint_functions. The agent must infer the distinction from the name 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