Skip to main content
Glama

unreal_get_behavior_tree

Retrieves behavior tree asset information from an Unreal Engine 5 project, letting AI clients inspect tree structure and properties for debugging or workflow automation.

Instructions

Get behavior tree 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_behavior_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 only restates the name. It does not confirm read-only behavior, say what identifier must be supplied (asset path vs. asset name), or describe scope such as whether it returns graph structure or only top-level metadata.

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?

It is a single short, front-loaded sentence with no filler wording. The problem is under-specification rather than verbosity, so it is efficient but barely informative.

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 here. Still, with zero annotation coverage, an opaque 'params' object at 0% schema coverage, and no behavioral or usage detail, the description is not sufficient to invoke this tool 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 description coverage is 0% and the single 'params' property is entirely untyped with no sub-properties, leaving no documented arguments. The description adds no information about what to pass, 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.

Purpose3/5

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

The verb 'Get' and resource 'behavior tree asset' are stated, and 'asset info' hints that it targets the asset rather than a runtime instance, which separates it loosely from siblings like unreal_get_ai_controller or unreal_get_blackboard. However 'info' is unspecified, so an agent cannot tell what aspect of the behavior tree is returned.

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 when another sibling tool would be the better choice. The agent is left to infer everything from the tool 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