Skip to main content
Glama

unreal_add_blueprint_function

Add a Blueprint function graph to Unreal Engine 5 Blueprints, enabling AI clients to create callable functions and automate editor workflows.

Instructions

Add a Blueprint function 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_add_blueprint_function"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 burden, and it only implies mutation via the word 'Add.' It does not say what asset is modified, whether the operation is undoable, what happens if the graph already exists, or what permissions auth is required. The phrase 'function graph' is the sole behavioral hint.

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

Conciseness2/5

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

It is a single short sentence with no wasted words, but here brevity is under-specification rather than conciseness: the one line conveys almost nothing an agent needs. There is no front-loaded scope, precondition, or payload hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with an opaque nested required parameter and an output schema, the description should at minimum identify the target asset and payload shape. It supplies neither, and with no annotations to fall back on, the definition is effectively unusable without trial and error.

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?

Schema description coverage is 0%, and the single required parameter is an untyped, undescribed 'params' object, so the description must compensate and does not. It gives no hint of the expected key names (blueprint path, function name, inputs, outputs), 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 says 'Add a Blueprint function graph,' which gives a verb ('Add') and a resource ('Blueprint function graph') and reads differently from siblings such as unreal_add_blueprint_variable or unreal_add_blueprint_event. However, it is ambiguous whether the call creates a function, a graph, or both, and the required 'params' payload is never characterized, so the agent cannot picture the outcome.

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 statement of when to use this tool, no prerequisites (e.g., that a Blueprint asset must already exist), and no pointer to related siblings like unreal_create_blueprint_node or unreal_get_blueprint_graphs. The agent must infer the whole usage context 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