Skip to main content
Glama

unreal_create_blueprint_macro

Creates a Blueprint macro graph in Unreal Engine to encapsulate reusable logic for Blueprint workflows.

Instructions

Create a Blueprint macro 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_create_blueprint_macro"
  }
}

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?

No annotations are supplied, so the description carries the full behavioral burden and delivers almost nothing: it does not say what asset is mutated or created, whether the macro is persisted/saved, what permissions or editor context are required, or what happens to an existing graph of the same name. The single word 'Create' is the only behavioral signal.

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, waste-free sentence, which is structurally fine. But the brevity is under-specification rather than economy — the sentence is too thin to support correct invocation.

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?

Wrong placeholder — recalculated below.

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 one required parameter is a bare 'params' object with 0% schema description coverage, no type, and no nested structure, and the description adds no meaning about what belongs inside it. This is the worst case: an opaque required payload with neither schema nor prose explaining it.

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 gives a specific verb and resource ('Create a Blueprint macro graph'), so the basic operation is identifiable. However, it offers no differentiation from near-identical siblings such as unreal_create_blueprint_node or unreal_create_blueprint, leaving ambiguity about what a 'macro graph' is versus those alternatives.

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, no prerequisite (e.g., an existing Blueprint asset to attach the macro to), and no mention of the sibling tools an agent should consider instead. The agent must infer everything 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