Skip to main content
Glama

unreal_get_blackboard

Retrieve blackboard asset information from an Unreal Engine 5 project to inspect AI behavior data and support debugging or editing workflows.

Instructions

Get blackboard asset info.

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

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, and it delivers almost nothing. "Get" weakly implies a read-only lookup, but there is no statement about permissions, whether an editor session or loaded asset is required, or what happens when the blackboard 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 waste, but here brevity comes from under-specification rather than disciplined editing. It is appropriately sized only in the sense that there is nothing extra to cut.

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. Still, for a tool whose only input is an undocumented params object and which competes with many similar get_* tools, the description leaves the caller without enough information to invoke it confidently.

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

Parameters2/5

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

Schema coverage is 0% and the single required parameter is an untyped "params" object with no properties documented. The description does not compensate by explaining that params should carry a blackboard asset reference or path, so the caller must infer the argument shape entirely.

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?

The description pairs a generic verb ("Get") with a specific resource ("blackboard asset info"), so the domain is identifiable. However, it does not say what kind of info (keys, values, defaults, mappings) or distinguish this from adjacent tools like unreal_get_behavior_tree or unreal_get_asset_info, leaving the agent to guess the scope.

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, no prerequisites, and no mention of alternatives. The agent gets no signal about whether this is the right call for inspecting AI blackboard data versus the behavior tree or generic asset tools in the sibling list.

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