Skip to main content
Glama

unreal_get_blueprint_variables

Lists Blueprint variables in Unreal Engine so AI clients can inspect a Blueprint's data before editing or debugging.

Instructions

List Blueprint variables.

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

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 provided, so the description carries the full disclosure burden, yet it says nothing about read-only semantics, permissions, or failure behavior for an invalid or missing Blueprint. It only implies a read operation via the verb "List".

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 four-word sentence is front-loaded and free of filler, but its brevity reflects under-specification rather than disciplined concision. Nothing is wasted because almost nothing is said.

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 described, but the opaque required params object combined with zero annotations leaves the agent without enough information to invoke the tool correctly. For a tool in a large Blueprint-related sibling set, this is a significant gap.

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 "params" property is defined with no type or sub-properties, so the schema offers no semantics at all. The description does not compensate by explaining what params must contain (e.g., a Blueprint path or name).

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?

"List Blueprint variables" names a specific verb (list) and resource (Blueprint variables), so an agent knows the general operation. It does not differentiate itself from siblings such as unreal_get_blueprint_functions or unreal_get_blueprint, nor does it clarify whether the listing is project-wide or scoped to a single Blueprint.

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 unreal_get_blueprint, unreal_get_blueprint_functions, or unreal_analyze_blueprint_relationships. No prerequisites, no exclusions, and no mention of what the required params argument must contain.

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