Skip to main content
Glama

set_blackboard_key_subsettings

DestructiveIdempotent

Sets the type-specific filter (base class or enum type) for an existing blackboard key on a UBlackboardData asset and saves it.

Instructions

Constrain an existing blackboard key's subsettings on a UBlackboardData asset and save. This is the SECOND HALF of add_blackboard_key, which only sets EntryName/KeyType/bInstanceSynced: it fills the per-type filter the editor would otherwise make you pick by hand -- BaseClass for an Object/Class key, EnumType for an Enum key. At least one of base_class / enum_type is required, and the one you supply must match the key's type.

Returns: { blackboard_path: string, key_name: string, key_type: string, base_class: string?, enum_type: string?, enum_name: string?, already_set: bool, saved: bool, save_error: string?, keys: [...] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
key_nameYesName of the existing key to constrain.
enum_typeNoEnum path/name (e.g. "/Script/Engine.ECollisionChannel") for an Enum key (optional).
base_classNoClass path/name (e.g. "/Script/Engine.Actor" or "Actor") for an Object/Class key (optional).
blackboard_pathYesPath to the UBlackboardData asset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds value beyond these by noting the asset is saved ('and save') and disclosing the result fields (already_set, saved, save_error) that signal mutation outcome, which matters for a destructive write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the sibling relationship, then the constraint, then the return shape. Slightly dense but every block earns its place, and the return shape is useful given there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers what it changes, the prerequisite relationship, the required constraint, and the returned fields including save_error. Nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: base_class applies to an Object/Class key and enum_type to an Enum key, they are mutually type-constrained, and at least one is required. This exceeds the schema's per-param text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb (constrain), resource (blackboard key subsettings), and target asset (UBlackboardData), then explicitly positions itself as the 'SECOND HALF of add_blackboard_key'. An agent can distinguish it from that sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the when: it fills the per-type filter left by add_blackboard_key, requiring at least one of base_class/enum_type and matching the key's type. The relationship to the prerequisite sibling and the conditional requirement are spelled out.

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