Skip to main content
Glama

unreal_get_blueprint_nodes

Lists nodes in a Blueprint graph, enabling users to inspect Blueprint structure and identify logic for debugging or editing.

Instructions

List nodes in a Blueprint graph.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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; 'List' implies a read operation but nothing confirms it is read-only. It does not disclose pagination, filtering, failure behavior for missing graphs, or whether the graph must already be open/loaded.

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 description is a single front-loaded sentence with no wasted wording, but its brevity reflects under-specification rather than disciplined conciseness. It is structurally clean but too thin to guide invocation.

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. However, the definition leaves the sole parameter completely undocumented and supplies no behavioral context for a tool that reads Blueprint graph structure, making it incomplete relative to the complexity of the task.

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?

The single required 'params' parameter has 0% schema description coverage and is a bare object with no documented shape. The description only indirectly implies that a Blueprint graph must be identified, without naming the parameter or explaining its expected format.

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 states a specific verb (List) and resource (nodes in a Blueprint graph), which is clear enough to distinguish it from get_blueprint_node_details and get_blueprint_graphs. It does not explicitly name or differentiate against any sibling, so it stops short of a 5.

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 tool versus alternatives such as unreal_get_blueprint_node_details or unreal_get_blueprint_graphs. No prerequisites, exclusions, or typical scenarios are given.

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