Skip to main content
Glama

unreal_get_blueprint_functions

Retrieves all functions defined in a Blueprint to inspect callable nodes and support editing or debugging workflows.

Instructions

List Blueprint functions.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 behavioral burden, yet it discloses nothing beyond the bare action. It does not state that this is a read-only operation, whether it requires an asset path or open editor context, whether results include inherited functions, or any pagination/limit behavior. Only the verb "List" weakly implies a safe read.

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?

The single sentence is front-loaded and free of padding, but here brevity reflects under-specification rather than efficiency. The one line that exists does not earn the tool a callable definition.

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-value documentation is fairly excused, but the input side is entirely opaque and there are no annotations to fall back on. For a tool whose only parameter is a required, undocumented object, the description leaves the essential call contract missing.

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 single required parameter is an untyped "params" object with no properties and 0% schema description coverage, and the description adds nothing about what must go inside it. An agent cannot determine from either source what identifier (asset path, Blueprint name, GUID) to supply, making the tool effectively uncallable 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?

"List Blueprint functions" names a specific verb (list) and resource (Blueprint functions), but it does not distinguish this from close siblings such as unreal_get_blueprint_graphs, unreal_get_blueprint_nodes, or unreal_get_blueprint_variables. Nor does it say which Blueprint is being targeted or what scope a function list covers.

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 when-to-use guidance at all: no prerequisites (does the Blueprint need to be loaded/compiled?), no statement of when to prefer unreal_get_blueprint_graphs or unreal_get_blueprint_variables instead, and no exclusions. The agent must guess 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