Skip to main content
Glama

unreal_add_blueprint_component

Adds a component to a Blueprint's Simple Construction Script (SCS), enabling AI clients to build and modify Blueprint component hierarchies in Unreal Engine 5 projects.

Instructions

Add a component to a Blueprint SCS.

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

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not say whether this mutates the Blueprint asset in memory only, whether a compile/save is required afterwards, what happens if a component of the same name exists, or whether permissions or an editor session are needed — all critical for a mutation operation on an asset.

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?

One short, front-loaded sentence with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. There is no structure beyond the single clause to guide a caller.

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, but for a mutation tool with zero annotation coverage and an opaque single-object parameter, the definition is far too thin. It leaves the agent without the information needed to invoke the tool correctly.

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 schema exposes a single untyped "params" object with no properties and 0% description coverage. The description says nothing about what must go inside params (blueprint path, component class, parent component, desired variable name), so the agent cannot construct a valid call from either source.

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 ("Add a component") and scopes it to a "Blueprint SCS", which distinguishes it from the sibling unreal_add_component (a plain component) and from the blueprint-variable/event/function siblings. The only weakness is reliance on the unexplained acronym "SCS" (Simple Construction Script).

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 unreal_add_component or unreal_add_blueprint_variable, no mention of prerequisites such as the target Blueprint asset being open or loaded, and no note on ordering relative to compilation. The agent must infer all of this from the one-line purpose statement.

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