Skip to main content
Glama

unreal_remove_blueprint_variable

Deletes a Blueprint variable from an Unreal Engine project to remove unused or obsolete variables and keep Blueprints organized.

Instructions

Remove a Blueprint variable.

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

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 supplied, the description carries the full burden of behavioral disclosure and delivers almost nothing beyond the verb. It does not say whether removal is irreversible, what happens to graph nodes or references bound to the variable, whether the change must be saved or compiled afterward, or what errors occur when the variable is missing.

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 single sentence is front-loaded and free of filler, so there is nothing to trim. However, its brevity reflects under-specification rather than economy, leaving no room for the operational detail this tool needs.

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 destructive mutation with no annotations and a completely undocumented parameter object, the definition is far too thin for the agent to invoke it safely or 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?

Schema coverage is 0% and the single parameter is an opaque, untyped "params" object with no declared properties. The description adds no information about what that payload must contain (Blueprint path/name, variable name, confirmation flags), so an agent cannot 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.

Purpose4/5

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

The description states a specific verb and resource ("Remove a Blueprint variable"), which an agent can readily distinguish from the add_blueprint_variable sibling by verb alone. It stops short of any explicit sibling differentiation or scope statement, so it does not reach 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_delete_blueprint or unreal_get_blueprint_variables, nor any stated preconditions (does the Blueprint need to be open? compiled? saved afterward?). The agent must infer the entire usage context.

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