Skip to main content
Glama

ue_cpp_class_create

Create a compilable C++ class in the Unreal project module, adding properties and functions that are accessible from Blueprints. Automatically sets up the C++ module if the project is Blueprint-only.

Instructions

Genera una classe C++ compilabile nel modulo del progetto.

È la risposta al limite principale di questo MCP: i grafi Blueprint non sono scrivibili da Python, ma la logica può stare in C++ e arrivare ai Blueprint per ereditarietà. Flusso completo:

ue_cpp_class_create -> ue_editor_close -> ue_build_start ->
ue_build_status (finché running=false) -> ue_editor_open ->
ue_reparent_blueprint

Se il progetto è Blueprint-only, il modulo C++ (Build.cs, Target.cs, IMPLEMENT_PRIMARY_GAME_MODULE, voce Modules nel .uproject) viene creato.

Args: uproject: percorso del file .uproject. class_name: nome senza prefisso, es. "DoorBase" -> ADoorBase. parent_class: "Actor", "Pawn", "Character", "ActorComponent", "GameModeBase", "PlayerState", ... module: nome del modulo C++; default il nome del progetto. properties: lista di dict con name, type (es. "float", "FVector", "TObjectPtr"), e opzionali category, default, replicated, rep_notify, read_only. Le proprietà replicate generano anche GetLifetimeReplicatedProps e i DOREPLIFETIME. functions: lista di dict con name, return_type, params, specifiers (default BlueprintCallable), body. Le funzioni BlueprintCallable diventano chiamabili dai grafi Blueprint. with_tick: abilita il Tick (di default è spento, come conviene). force: sovrascrive i file se esistono già.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNo
moduleNo
uprojectYes
functionsNo
with_tickNo
class_nameYes
propertiesNo
parent_classNoActor
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and discloses key behaviors: files are created/overwritten (with force), generated code includes replication properties and BlueprintCallable functions, and for Blueprint-only projects it sets up the C++ module. It does not mention required auth or cleanup.

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

Conciseness4/5

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

The description is well-structured with a purpose explanation, a clear workflow, and a bulleted list of parameters. It is slightly verbose but every sentence adds value. Front-loads the main purpose.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is fully complete. It explains the overall workflow, each parameter in detail, and edge cases like Blueprint-only projects. No significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description provides essential meaning for all parameters. It explains class_name naming convention, parent_class examples, properties structure with replication effects, functions with specifiers, and force overwrite behavior. This goes well beyond schema property names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates a compilable C++ class in a project module, specifying the verb 'genera' and the resource 'classe C++ compilabile'. It distinguishes from sibling Blueprint tools by explaining it overcomes the limitation that Blueprint graphs are not writable from Python.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a complete workflow and explains when to use the tool (to move logic to C++ for Blueprint inheritance). It implicitly excludes alternatives like ue_create_blueprint but does not explicitly name them or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FFZackFair92/unreal-engine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server